claims-and-scope-discipline
Skill1 starsChanged 2 months agoNo licenceView on GitHub
Verifying a written claim about code (a review finding, a ticket, a plan step) before acting on it, and deciding what a fix may touch. Use when a citation does not match the code, when a ticket prescribes the fix, quantifies blast radius, reads Done, belongs to another lineage, or quotes a SHA, file count or tooling claim, when a defect crosses a scope boundary, when two tickets describe one defect, when a diff looks too small to review, when verifying a claimed deletion, or a check that could not run or could not have failed, when a PR shows no CI checks, when a rule and a measurement disagree, when a claim is relayed between sessions, when shared test infrastructure changes, when a change implies deploy-time ordering, when several findings cluster in one area, or at an integration merge of separately-reviewed branches. Not grouping already-verified findings into a fix plan (root-cause-fix), orchestration control flow or agent briefing (plan-rollout), or git/worktree mechanics (git-worktree-topology).
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-styleSkill
- benchmark-code-graphsSkill
- bug-reportSkill
- context7-mcpSkill
- dreamSkill
- dual-scoped-review-plansSkill
- git-worktree-topologySkill
- improve-memorySkill
- plan-and-reviewSkill
- plan-docsSkill
- plan-rolloutSkill
- reviewSkill
- root-cause-fixSkill
- send-resultsSkill
- session-analysisSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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.

