Skill

review-pr

Reviews PRs or branch diffs using knowledge graph for structural context, blast-radius analysis, risk assessment, test coverage, and structured file-by-file output.

Git

git-workflow

code-quality

npx claudepluginhub nicmarti/claudette

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Perform a comprehensive code review of a pull request or branch diff using the knowledge graph.

SKILL.md

Similar Skills

review-delta

Reviews only code changes since last commit using graph-based impact analysis and blast radius detection. Provides token-efficient context for focused reviews of bugs, style, tests, and affected files/functions.

claudette

gitnexus-pr-review

23.0k

Reviews pull requests by analyzing diffs with GitNexus: detects affected flows/symbols, computes blast radius, checks test coverage, and assesses merge risk.

gitnexus

pr-reviews

Reviews GitHub pull requests using gh CLI, analyzing diffs for code quality, security, testing, best practices, and providing structured feedback.

odin

Stats

Stars19

Forks3

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Review PR

Perform a comprehensive code review of a pull request or branch diff using the knowledge graph.

Token optimization: Before starting, call get_docs_section(section_name="review-pr") for the optimized workflow. Never include full files unless explicitly asked.

Steps

Identify the changes for the PR:

If a PR number or branch is provided, use git diff main...<branch> to get changed files
Otherwise auto-detect from the current branch vs main/master

Update the graph by calling build_or_update_graph(base="main").

Get the full review context by calling get_review_context(base="main").

Analyze impact by calling get_impact_radius(base="main").

Deep-dive each changed file:

Read the full source of files with significant changes
Use query_graph(pattern="callers_of", target=<func>) for high-risk functions
Use query_graph(pattern="tests_for", target=<func>) to verify test coverage

Generate structured review output:

## PR Review: <title>

### Summary
<1-3 sentence overview>

### Risk Assessment
- **Overall risk**: Low / Medium / High
- **Blast radius**: X files, Y functions impacted
- **Test coverage**: N changed functions covered / M total

### File-by-File Review
#### <file_path>
- Changes: <description>
- Impact: <who depends on this>
- Issues: <bugs, style, concerns>

### Recommendations
1. <actionable suggestion>

Review PR

Perform a comprehensive code review of a pull request or branch diff using the knowledge graph.

Token optimization: Before starting, call get_docs_section(section_name="review-pr") for the optimized workflow. Never include full files unless explicitly asked.

Steps

Identify the changes for the PR:
- If a PR number or branch is provided, use git diff main...<branch> to get changed files
- Otherwise auto-detect from the current branch vs main/master
Update the graph by calling build_or_update_graph(base="main").
Get the full review context by calling get_review_context(base="main").
Analyze impact by calling get_impact_radius(base="main").
Deep-dive each changed file:
- Read the full source of files with significant changes
- Use query_graph(pattern="callers_of", target=<func>) for high-risk functions
- Use query_graph(pattern="tests_for", target=<func>) to verify test coverage

Generate structured review output:

## PR Review: <title>

### Summary
<1-3 sentence overview>

### Risk Assessment
- **Overall risk**: Low / Medium / High
- **Blast radius**: X files, Y functions impacted
- **Test coverage**: N changed functions covered / M total

### File-by-File Review
#### <file_path>
- Changes: <description>
- Impact: <who depends on this>
- Issues: <bugs, style, concerns>

### Recommendations
1. <actionable suggestion>