gitnexus-pr-review
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: \"Review this PR\", \"What does PR #42 change?\", \"Is this PR safe to merge?\"
Best for Code reviewersWorks with GitHub
⌘source
- author
@abhigyanpatwari- language
- TypeScript
★28kstars
3.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Analyzes PR diffs to map changes to affected execution flows
- ·Assesses upstream impact and blast radius for changed symbols
- ·Provides context on callers and callees of key symbols
- ·Checks affected execution flows from repository processes
- ·Includes a checklist for systematic PR review
Use Cases
- →Reviewing a colleague's pull request before merging
- →Understanding the scope and impact of changes in PR #42
- →Assessing the safety and risk of merging a specific PR
- →Identifying missing test coverage for changes in a pull request
- →Evaluating the blast radius of code changes before deployment
Best for
- ✓Code reviewers
- ✓Engineering leads
- ✓Release managers
Not ideal for
- !Non-GitHub repositories
- !One-line typo fixes
FAQs
name
gitnexus-pr-review
description
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
PR Review with GitNexus
When to Use
- "Review this PR"
- "What does PR #42 change?"
- "Is this safe to merge?"
- "What's the blast radius of this PR?"
- "Are there missing tests for this PR?"
- Reviewing someone else's code changes before merge
Workflow
1. gh pr diff <number> → Get the raw diff
2. gitnexus_detect_changes({scope: "compare", base_ref: "main"}) → Map diff to affected flows
3. For each changed symbol:
gitnexus_impact({target: "<symbol>", direction: "upstream"}) → Blast radius per change
4. gitnexus_context({name: "<key symbol>"}) → Understand callers/callees
5. READ gitnexus://repo/{name}/processes → Check affected execution flows
6. Summarize findings with risk assessment
If "Index is stale" → run
npx gitnexus analyzein terminal before reviewing.
Checklist
- [ ] Fetch PR diff (gh pr diff or git diff base...head)
- [ ] gitnexus_detect_changes to map changes to affected execution flows
- [ ] gitnexus_impact on each non-trivial changed symbol
- [ ] Review d=1 items (WILL BREAK) — are callers updated?
$install
1-click copynpx skills add abhigyanpatwari/GitNexus --skill gitnexus-pr-reviewSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.