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.

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.

check-onboarding

check-payments

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-product-standards

check-quality

Validates database access follows repository pattern, detects god-trait regression, ensures focused repositories

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.

Scan the codebase for potential secret leaks before commits.

This skill should be used when checking for naming conflicts between local skills (~/.claude/skills) and plugin-provided skills (~/.claude/plugins). Use to identify duplicate or similarly named skills that may cause inconsistent agent behavior.

Validate spots.json for common issues including missing fields, invalid URLs, duplicate entries, and data consistency problems

check-stripe

Validate code against Team Codex standards. Use when (1) before creating commits, (2) during verification phase, (3) quality gate enforcement.

Verify all site content aligns with the five foundational tenets. Use monthly or after major content additions.

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.

check-virality

check

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

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

Quick data freshness check. Use when the user asks if data is up to date, when a table was last updated, if data is stale, or needs to verify data currency before using it.

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

**You are an autonomous agent. You make decisions. You do not ask questions. You do not stop.**

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

Build resumable state-machine workflows with checkpoint patterns, progress preservation, and automatic recovery for complex multi-phase operations that need to survive interruptions, timeouts, and failures.

Save context state - auto-triggered every 5 tasks

Standard Operating Procedure for /fix-ci phase. Fix CI/deployment blockers after PR creation.

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.

Manage Checkvist tasks, checklists, and notes using checkvist-cli. Use when the user wants to work with Checkvist.com data, including viewing/creating/updating checklists, hierarchical tasks, or task notes.

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

Use when writing Apple Shortcuts as code using Cherri language. Covers syntax, actions, compilation, and common patterns.

Guide for analyzing chess positions from images and determining optimal moves. This skill should be used when asked to find the best move, checkmate, or tactical solution from a chess board image. It provides structured approaches for image-based chess analysis, piece detection calibration, position validation, and move verification.

This skill should be used when developing or modifying dotfiles using chezmoi. Covers using .chezmoidata for configuration data and modify_ scripts (or run_onchange_after_ scripts for symlinked directories) for non-destructive file merging. Particularly useful when needing to configure application settings without overwriting user preferences.

Manage dotfiles using chezmoi. Use when creating, modifying, or deploying dotfiles, shell functions, or configuration files in this repository.

Chezmoi dotfile management expertise

Query and download datasets from the City of Chicago Data Portal using the Socrata Open Data API (SODA) and SoQL.