change-verification
Skill363 starsChanged 13 days agoMITView on GitHub
Select and report proportionate checks for a pyfixest diff before handoff, or when verification is requested. Reuse valid evidence; this is not a trigger to rerun every suite.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- implementation-strategySkill
- pr-handoffSkill
- pr-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 11
Use the selection matrix to identify required evidence.
≈ “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
Verify a change
Inspect the complete diff, including relevant uncommitted and untracked files, against the intended base.
Use the selection matrix to identify required evidence. Read only the applicable testing sections: numerical references and release contract for numerical work, benchmarks for performance-relevant changes, or link/configuration checks for guidance.
Inventory evidence already available for this code state, including CI. Run the missing checks under runtime tiers. A later handoff or prose edit does not itself invalidate a passing code check.
Report the result under verification reporting. Resolve failures and material uncertainty; distinguish completed local work from outstanding merge evidence. Do not claim a skipped comparison passed.
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.