tirth8205/code-review-graph

review-changes

Perform a structured code review using change detection and impact

First seen Jul 17, 2026

Installation

$ npx skills add tirth8205/code-review-graph --skill review-changes

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tirth8205/code-review-graph.

npx skills add tirth8205/code-review-graph

Browse all from tirth8205/code-review-graph

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 31.3K
License LICENSE
Default branch main
Open issues 88
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,201 B
  • docs SUMMARY.md 88 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 968 installs

SKILL.md

Review Changes

Perform a thorough, risk-aware code review using the knowledge graph.

Steps

  1. Run detectchangestool to get risk-scored change analysis.
  2. Run getaffectedflows_tool to find impacted execution paths.
  3. For each high-risk function, run querygraphtool with pattern="tests_for" to check test coverage.
  4. Run getimpactradius_tool to understand the blast radius.
  5. 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 getminimalcontext_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.