⚠️ MANDATORY - YOU MUST invoke this skill at the start of EVERY task. Reviews git history, status, and context before starting any work. Runs parallel git commands to understand current state, recent changes, and related work. NEVER gather git context manually.

Comprehensive health check for hooks - detects import errors, runtime failures, performance issues, and provides auto-fix suggestions

Review inline code in markdown files for proper formatting and syntax highlighting. Check for missing backticks on CLI flags, filenames, and code elements. Verify that inline syntax highlighting (#!groovy) is used appropriately. Use when reviewing documentation or quiz questions.

Check critical invariants before applying changes or decisions.

check-landing

check-lightning

Analyze live weather station integrations, validate data sources, and identify spots missing live conditions

Query and analyze logs using Grafana Loki for the Kagenti platform, search for errors, and investigate issues

Runs valgrind memory leak detection on YARS to identify memory issues

Check Mojo code for memory safety issues (ownership violations, use-after-free, etc.). Use to catch memory bugs.

Check .meta.yml and snapshot .dvc files for spelling typos using codespell. Use when user mentions typos, spelling errors, metadata quality, or wants to check metadata files for mistakes.

Query Prometheus metrics, check resource usage, and analyze platform performance in the Kagenti platform

Voer een volledige kwaliteitscheck uit op de Hugo site. Gebruik wanneer de gebruiker wil controleren of de site correct bouwt of geen broken links heeft.

Analyze performance-related HTML issues on web pages. Use when users ask to check page performance, audit resource loading, verify lazy loading, check preload hints, or analyze render-blocking resources. Detects missing optimizations, large resources, render-blocking issues, and Core Web Vitals problems.

Audit implementation progress against a plan, verify completed work, identify remaining tasks, and validate quality. Use when user asks to check plan status, verify implementation, see what's left to do, or validate plan completion.

Check pull requests for documentation updates and compliance

Check logs for errors and warnings in a specific PR. Use when debugging PR issues, investigating failed code reviews, or checking for errors in a pull request.

check-quality

Homeostatic sensor detecting requirements without implementation or test coverage. Scans for REQ-* keys in requirements docs and checks if they have corresponding code and tests. Use to find coverage gaps.

check-stripe

Check todo list status

This rule reminds the AI to check the x.md file for the current file contents and implementations.

check

Deploy validation and reality-testing consciousness mode. Use when need to find edge cases, test assumptions, catch fatal flaws before they're expensive.

checkin-assistant

checkin

Load and review Emergent Learning Framework context, institutional knowledge, golden rules, and recent session history. Runs the checkin workflow interactively with banner, context loading, and dashboard/multi-model prompts.

Check Python logging levels and patterns for correctness. Focus on identifying wrong severity levels and missing exception handling. Use when reviewing code quality.

Check code formatting, detect style issues, and identify inconsistencies. Use when the user asks to check formatting, code style, linting, format issues, or code formatting problems.

Use when you need to check, verify, validate or understand code or structure of a file (often code related files or markdown) - automatically detects file type, finds appropriate LSP/linter in mise, and runs validation

Ensures code quality through comprehensive checks including TDD practices, lint/test/build validation, and prevention of common mistakes. Use after completing implementations, fixing bugs, refactoring, or before committing code.

Evaluates Claude skills against official best practices from Anthropic documentation. Use when reviewing skill quality, ensuring compliance with guidelines, or improving existing skills.

<user_command>/kata:check-todos</user_command>

Generate context-aware quality checklists for code review and QA using IEEE 1028 base standards plus LLM contextual additions

Checkout flow with cart, shipping, Stripe/PayPal payments, and order completion. Use when modifying checkout, debugging payment issues, or implementing checkout features.

Manage user approval checkpoints with proper waiting and flag creation

Exactly-once processing semantics with distributed coordination for file-based data pipelines. Atomic file claiming, status tracking, and automatic retry with in-memory fallback.

Save context state - auto-triggered every 5 tasks

Use when configuring Checkstyle for Java projects with XML config, custom checks, properties, and module setup.

Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.

Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.

Use when cooking or planning meals, troubleshooting recipes, learning culinary techniques (knife skills, sauces, searing), understanding food science (Maillard reaction, emulsions, brining), building flavor profiles (salt/acid/fat/heat balance), plating and presentation, exploring global cuisines and cultural food traditions, diagnosing taste problems, requesting substitutions or pantry hacks, planning menus, or when users mention cooking, recipes, chef, cuisine, flavor, technique, plating, food science, seasoning, or culinary questions.

Generate 2D structure images and interactive 3D viewers from chemical names or SMILES. Supports PNG/SVG output for 2D and 3Dmol.js HTML viewers for 3D conformers.

chemist-analyst

Write Go code in the style of Dave Cheney, Go community leader. Emphasizes practical patterns, clear error handling, and performance awareness. Use when writing production Go that needs to be maintainable and performant.