Check

What it does

This skill, named "Check," automates verification of code changes against predefined checks written in Markdown files. It gathers context by creating temporary files containing git diffs and commit logs, then launches background agents to review these changes based on the instructions within those check files. The skill aggregates results and presents a summary table to the user, highlighting any failures for triage.

When to use it

• To automatically enforce code conventions during development.
• To identify potential security vulnerabilities in code changes.
• To ensure test quality before merging code.
• When working on projects with established coding standards and automated checks.
• For continuous integration workflows where consistent code review is needed.

Key capabilities

• Diff Generation: Creates temporary files containing git diffs (limited to 3000 lines) and commit logs.
• Check Discovery: Identifies available check files from the .continue/checks/*.md directory.
• Parallel Execution: Runs checks concurrently using background agents.
• Structured Reporting: Provides a summary table of check results (PASS or FAIL).
• Targeted Feedback: Presents individual findings for failed checks via AskUserQuestion.

Example prompts

• "Run all available checks."
• "Verify the latest changes against the code conventions and security checks."
• "Check my work for test quality issues."

Tips & gotchas

• The skill relies on git being installed and configured.
• Checks are defined in Markdown files located within the .continue/checks/ directory.
• Large diffs (over 3000 lines) will be truncated, potentially impacting the accuracy of some checks.