check
Local Check Runner
Run every .continue/checks/*.md check against the current changes, just like the GitHub PR checks do in CI.
Workflow
1. Gather context (write to disk, NOT into your context)
- Run
git diff main...HEADand write it to/tmp/check-diff.patch. If the diff is empty, also trygit diff --cachedandgit diff.- Cap the diff: If the diff exceeds 3000 lines, truncate it to 3000 lines when writing. Add a final line:
\n... (diff truncated at 3000 lines). - Use a single bash command like:
git diff main...HEAD | head -3000 > /tmp/check-diff.patch
- Cap the diff: If the diff exceeds 3000 lines, truncate it to 3000 lines when writing. Add a final line:
- Run
git log main..HEAD --onelineand write it to/tmp/check-log.txt. - If there are no changes at all, tell the user and stop.
- Do NOT read these files back into your own context. The sub-agents will read them directly.
2. Discover checks
More from continuedev/skills
writing-checks
Write Continue check files that review pull requests with AI agents. Use when the user asks to create, write, or generate a check, or wants to enforce a convention on PRs.
138scan
Scans the codebase against another skill's criteria using a parallel agent team. Use when the user says /scan <skill-name> to audit code quality, find violations, or assess conformance to best practices.
55all-green
Addresses all PR review comments, resolves merge conflicts, and fixes failing CI checks to get the PR ready to merge. Use when the user wants to make their PR "all green" or ready for merge.
46polish-repo
Polish an open-source repository with branding, community files, README overhaul, OG card, usage skill, PR checks, and publishing setup. Designed as a reusable template for Continue repos.
25