
review changes
Perform a structured code review using change detection and impact
- Installs
- 1.1K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/tirth8205/code-review-graph --skill review-changes- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads review changes automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Review Changes
Review a change set with risk scores and blast radius from the knowledge graph.
Steps
- Call
detect_changes_toolfor risk-scored changed functions, test gaps and affected flows. - Call
get_affected_flows_toolonly when you need the steps of an affected flow. - For each high-risk function, call
query_graph_toolwithpattern="tests_for"to check test coverage. - Call
get_impact_radius_toolwhen the blast radius is not clear from step 1. - Suggest specific test cases for untested changes.
Output Format
Group findings by risk level (high, medium, low). For each finding give what changed and why it matters, its test coverage, and the suggested fix. End with a merge recommendation.
Token Efficiency Rules
- Call
get_minimal_context_tool(task="<your task>")before any other graph tool. - Pass
detail_level="minimal"wherever a tool accepts it. Use "standard" only when minimal is not enough. - Prefer a targeted
query_graph_toolcall over a broad listing call. - Budget: about five tool calls and 800 tokens of graph output per task.
- Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
FAQ
What does the review changes skill do?
Perform a structured code review using change detection and impact
How do I install review changes?
Run npx skills add https://github.com/tirth8205/code-review-graph --skill review-changes in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-changes/ (personal) or .claude/skills/review-changes/ (project).
Which AI agents can use review changes?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is review changes safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains review changes?
It is published by tirth8205 in tirth8205/code-review-graph. It has 1,057 recorded installs.
More from tirth8205/code-review-graph
build-graph
tirth8205/code-review-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
review-delta
tirth8205/code-review-graph
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
review-pr
tirth8205/code-review-graph
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
explore codebase
tirth8205/code-review-graph
Navigate and understand codebase structure using the knowledge graph
refactor safely
tirth8205/code-review-graph
Plan and execute safe refactoring using dependency analysis
debug issue
tirth8205/code-review-graph
Systematically debug issues using graph-powered code navigation
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.