wire-check
Skill0 starsChanged 39 days agoMITView on GitHub
Make important engineering checks authoritative by connecting existing lint, type, architecture, test, build, or generated-state checks to one normal contributor command and CI without duplicating policy.
In this repository16 other files it gives its agents.
- create-checkSkill
- decideSkill
- design-changeSkill
- design-moduleSkill
- groundSkill
- harden-boundarySkill
- harden-checkSkill
- intentSkill
- investigateSkill
- learnSkill
- pave-pathSkill
- ratchetSkill
- realizeSkill
- specifySkill
- validateSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Make CI authoritative: Ensure merge-gating CI invokes the canonical exhaustive command or the same constituent checks.
- Distinctive: line 17
Document one entry point: Keep agent/contributor guidance boring: name the authoritative command and any fast/full distinction.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wire Check
A guardrail that contributors and CI do not reliably execute is not an effective ratchet.
Work
- Map verification entry points. Inspect package/build scripts, CI workflows, hooks, task runners, monorepo affected commands, and documented contributor commands. Identify the command that should define repository health; reuse an existing
check,ci,validate, or equivalent when possible. - Find unwired or divergent checks. Identify important checks that exist but are absent from the umbrella command or CI, and CI paths that run materially different verification from local contributors.
- Compose, do not duplicate. Wire existing commands into one stable local entry point. Keep cheap feedback cheap; if the full suite is materially slow, preserve a fast
checkplus an exhaustivecheck:all/CI path rather than making agents avoid verification. - Make CI authoritative. Ensure merge-gating CI invokes the canonical exhaustive command or the same constituent checks. Hooks may improve latency but are not a substitute for CI because they are locally bypassable.
- Prove execution. Demonstrate the umbrella command reaches the target check. When safe, use the check's known negative fixture/mutation and show the authoritative path fails because of it, then restore and pass.
- Document one entry point. Keep agent/contributor guidance boring: name the authoritative command and any fast/full distinction. Do not copy every underlying rule into instructions.
Return
- Authoritative local command
- CI path
- Checks wired
- Fast/full split, if any
- Execution proof
- Remaining bypasses
Failure signals
Adding another parallel command instead of converging, relying only on pre-commit hooks, making the common check so slow it discourages iteration without justification, or claiming CI coverage without tracing the workflow to the actual command.
Done when
Important checks have an explicit, stable contributor entry point, CI executes the required authoritative verification, and execution has been demonstrated rather than inferred from configuration alone.
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.

