review-changes
Skill2 starsChanged 3 months agoMITView on GitHub
Perform a structured code review using change detection and impact
38 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- Lucface/claude-skillstheir own version, first seen Nov 16, 2026
- mlschodkowski/skillstheir own version, first seen Nov 16, 2026
- asymmetric-effort/convocateedited, first seen Nov 15, 2026
- todoist/todoist-clitheir own version, first seen Nov 15, 2026
- tirth8205/code-review-graphedited, first seen Nov 11, 2026
- Doist/todoist-aitheir own version, first seen Nov 9, 2026
Used with
Projects with it also use fix-bug, write-tests and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JetBrainsSkillfix-bug
End-to-end bug fix workflow for the Exposed project. Accepts a GitHub issue (#NUMBER), YouTrack issue (EXPOSED-NUMBER), or YouTrack URL (https://youtrack.jetbrains.com/issue/EXPOSED-NUMBER). Fetches the issue, creates a failing reproducer test, commits on a new branch, implements the fix, validates, and opens a PR. Use this skill whenever the user wants to fix a bug from an issue tracker, mentions a EXPOSED issue number, or references a GitHub issue to fix.
Also in 3 projects that use this
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
GoogleSkillto-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Also in 3 projects that use this
GoogleSkillto-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 3 projects that use this
MicrosoftSkillwriting-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Also in 3 projects that use this
- +3 more from google
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- tirth8205/code-review-graph★ 33k21% same
- asymmetric-effort/convocate★ 489% same
- exactbee/claude-code-workflow★ 179% same
Wrote their own version · 35
- docker/docs★ 4.7ksame name
- Doist/todoist-ai★ 565same name
- Doist/todoist-cli★ 332same name
- todoist/todoist-cli★ 332same name
- blockscout/frontend★ 310same name
- timothywarner-org/claude-code★ 223same name
- appclawhq/AppClaw★ 120same name
- munvard/dockterm★ 48same name
- uniffy-io/uniffy★ 24same name
- jjxmonster/skills★ 8same name
25 more not listed
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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/improve/agents/claude.mdCLAUDE.md
- skills/use-chatgpt/agents/claude.mdCLAUDE.md
- debug-issueSkill
- explore-codebaseSkill
- refactor-safelySkill
- building-gtd-domain-packsSkill
- get-things-doneSkill
- gtd-capability-routerSkill
- gtd-deliberationSkill
- improveSkill
- reaSkill
- use-chatgptSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 37 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run detect_changes_tool to get risk-scored change analysis.
- Very specific: line 13
Run get_affected_flows_tool to find impacted execution paths.
- Very specific: line 15
Run get_impact_radius_tool to understand the blast radius.
- Very specific: line 27
Start with get_minimal_context_tool(task="<your task>") before other graph tools.
- Very specific: line 28
Use detail_level="minimal" on all calls.
- Distinctive: line 30
Read the implementation and its tests before changing code.
“Common” is measured: kept by at least 6 in 10 of the 37 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
Review Changes
Perform a thorough, risk-aware code review using the knowledge graph.
Steps
- Run
detect_changes_toolto get risk-scored change analysis. - Run
get_affected_flows_toolto find impacted execution paths. - For each high-risk function, run
query_graph_toolwith pattern="tests_for" to check test coverage. - Run
get_impact_radius_toolto understand the blast radius. - For any untested changes, suggest specific test cases.
Output Format
Provide findings grouped by risk level (high/medium/low) with:
- What changed and why it matters
- Test coverage status
- Suggested improvements
- Overall merge recommendation
Token Efficiency Rules
- Start with
get_minimal_context_tool(task="<your task>")before other graph tools. - Use
detail_level="minimal"on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
- Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
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.

