run-checks
Skill1 starsChanged 14 days agoMITView on GitHub
Runs every automated check (file size, forbidden patterns, plan scope, lint, types, unit tests, migrations) on the changed files and prints ALL PASS or FAIL. Use after writing tests, after self-review, and before any commit or push.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- erikunha/vault-of-locitheir own version, first seen Nov 16, 2026
- agent-ecosystem/agent-skill-implementationtheir own version, first seen Nov 8, 2026
- hashicorp/design-systemtheir own version, first seen Oct 13, 2026
- fws94/product9-token-savertheir own version, first seen Oct 11, 2026
- thinkyou0714/codex-toolkittheir own version, first seen Jul 3, 2026
- rikeda71/cxbridgetheir own version, first seen Jun 1, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- hashicorp/design-system★ 519same name
- agent-ecosystem/agent-skill-implementation★ 6same name
- fws94/product9-token-saver★ 1same name
- rikeda71/cxbridge★ 1same name
- erikunha/vault-of-loci★ 0same name
- thinkyou0714/codex-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-ticket-workflow.mdcCursor rule
- .cursor/rules/10-general-standards.mdcCursor rule
- .cursor/rules/20-backend-standards.mdcCursor rule
- .cursor/rules/30-frontend-standards.mdcCursor rule
- .cursor/rules/40-database-standards.mdcCursor rule
- .cursor/rules/50-testing-standards.mdcCursor rule
- backend-implementSkill
- chatSkill
- codebase-exploreSkill
- db-migrationSkill
- frontend-implementSkill
- gitlab-mrSkill
- implementation-planSkill
- jira-createSkill
- mr-feedbackSkill
- mr-reviewSkill
- quick-fixSkill
- self-reviewSkill
- ticket-intakeSkill
- ticket-qaSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
When ALL PASS: paste the final summary lines into the PROGRESS.md log.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run checks
Steps
- From the repo root run:
bash .cursor/skills/run-checks/scripts/check_all.sh - The last line is either
ALL PASSorFAIL: <check names>. - On FAIL: scroll up to the first
--- <check>: FAILblock. Fix ONLY that cause, then run again. - Same error 3 times → stop and ask the human (show the error and what you tried).
- Not allowed, ever:
- editing these scripts, lint/type/test config, or
.agent/*.txtallowlists # noqa,# type: ignore,eslint-disable,@ts-ignore,pytest.mark.skip,xfail,xit(,.skip(/.only(/.todo(/.fixme(- deleting or weakening a test
- editing these scripts, lint/type/test config, or
- A failing test you did not write: check whether your diff touches the code it tests
(
git diff $(git merge-base origin/main HEAD) --stat). If it doesn't, STOP and report it to the human as possibly pre-existing. Don't "fix" unrelated tests. - When
ALL PASS: paste the final summary lines into the PROGRESS.md log.
Scripts (for reference; do not edit)
check_all.sh: runs the checks below for files changed vs$BASE_REF(defaultorigin/main); fails if that ref is missing. On a ticket branch it records the verdict and the exact content checked in.agent/work/<KEY>/last-check.txtcheck_size.sh: files ≤ 200 lines, React components ≤ 150check_guards.sh: debug code, ignore comments, skipped or removed tests, secrets, leftover stubs, swallowed errors, protected paths, edits to migrations already on maincheck_scope.sh: every changed file must be named in PLAN.mdcheck_backend.sh: ruff, ruff format, mypy on changed files + full pytest (local DB only), with coverage when pytest-cov is installedcheck_frontend.sh: tsc, eslint on changed files + full vitest, with coverage when@vitest/coverage-v8or-istanbulis installedcheck_coverage.sh: at least the minimum in.agent/coverage.txt(default 90%) of the changed production lines ran in those tests; skipped without a coverage reportcheck_migration.sh: alembic round trip of the changed migrations, single head, model drift (local DB only; also runs when models change)db_guard.sh: refuses a DB whose host isn't inLOCAL_DB_HOSTS(used by the two above)check_api_types.sh: the generated API types match the backend's OpenAPI schema (--writeregenerates them); skipped until set upproof_pack.sh: the MR's Proof section (verdict, red lines, changed files); refuses unless the lastALL PASSran on exactly HEAD's content. Used by /gitlab-mr and /mr-feedbackselftest.sh: tests these scripts, the mr-feedback scripts and the command hook. For humans changing them; not part of run-checksdoctor.sh: the setup checklist (tools,glab/ghlogin, the command hook, the self-tests). For humans; not part of run-checks
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

