change-review
Skill2 starsChanged 10 days agoMITView on GitHub
Review a git diff with file coverage, path-matched criteria, and falsify-before-report. Use when asked to review a pull request, a commit, or a working-tree diff. Do not use for a whole-tree engineering audit, session retrospective, or live service intake.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- hidetzu/claude-dev-templatetheir own version, first seen Nov 15, 2026
- YuY-QK/agent-kittheir own version, first seen Nov 15, 2026
- BurakD/ai-engineering-harnesstheir own version, first seen Nov 1, 2026
- assistant-ui/assistant-uitheir own version, first seen Oct 25, 2026
- alfonsusenrico/pakemtheir own version, first seen Oct 25, 2026
- yuanJewel/skillstheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- assistant-ui/assistant-ui★ 13ksame name
- goldenprofile/llm-skills★ 3same name
- flying-dice/pseudoscript★ 2same name
- yuanJewel/skills★ 2same name
- BurakD/ai-engineering-harness★ 1same name
- marinsokol5/change-review★ 1same name
- alfonsusenrico/pakem★ 0same name
- hidetzu/claude-dev-template★ 0same name
- straider911/claude-skills★ 0same name
- YuY-QK/agent-kit★ 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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-artifactSkill
- agent-discoverySkill
- agent-run-supervisionSkill
- api-contract-migrationSkill
- changelog-updateSkill
- ci-reviewSkill
- claims-auditSkill
- dependency-auditSkill
- derivation-auditSkill
- durable-cacheSkill
- engineering-auditSkill
- infer-conventionsSkill
- operational-signal-intakeSkill
- planned-releaseSkill
- preferred-stackSkill
- pressure-benchmarkingSkill
- public-surface-reconSkill
- rfc-processSkill
- security-auditSkill
- session-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Read the file. Cite line ranges that exist in the current tree.
- Distinctive: line 26
Use path-matched criteria.
- Distinctive: line 32
Do not restate what formatters, linters, and compilers already catch.
- Very specific: line 36
Use observed, inference, or artifact-missing as the evidence kind.
- Very specific: line 40
Write durable findings under docs/issues when the review is more than a chat pass.
- Distinctive: line 49
When a named skill is unavailable, preserve the finding and name the deeper review.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Change review
Review the changed files in a diff. This skill does not replace engineering-audit. It owns coverage of the change, not the whole tree.
Quick reference
list changed files -> mark skips -> path-matched criteria -> read the file -> cite existing lines -> falsify against the diff -> reportCoverage
Account for every changed file. Mark skipped files with a reason. Report coverage. Do not stop after the first high finding.
Read the file. Cite line ranges that exist in the current tree. A finding that cannot be placed is inference or artifact-missing.
Use path-matched criteria. Do not dump every language checklist into one prompt.
Falsify
Falsify each finding against the diff alone before reporting. Drop a finding the diff contradicts. Confirm concurrent invocation before a race. Confirm attacker control before a security finding.
Do not restate what formatters, linters, and compilers already catch. Missing tests remain a defect.
Kinds
Use observed, inference, or artifact-missing as the evidence kind. When security mode is also in scope, add the disposition defined by engineering-audit security mode.
Record
Write durable findings under docs/issues when the review is more than a chat pass. Follow docs-conventions. The chat report may be compact; the file stays plain prose.
Routing
engineering-auditfor whole-tree, pipeline, or product-mode review.claims-auditwhen the diff states material external facts.publish-checksbefore a pull request.session-reviewfor transcripts, not diffs.
When a named skill is unavailable, preserve the finding and name the deeper review.
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.

