skills.rest
ibytechaos
ibytechaosCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-pr-review

Reviews pull requests by mapping diffs to affected execution flows and blast radius via GitNexus.

1|Updated Oct 11, 2025
Search Tags:#code review#pull request#github#impact analysis#test coverage#blast radius#gitnexus
One-click install
npx skills add https://github.com/ibytechaos/claude --skill gitnexus-pr-review-ibytechaos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/ibytechaos/claude/tree/main/plugins/gitnexus/skills/gitnexus-pr-review
Command: npx skills add https://github.com/ibytechaos/claude --skill gitnexus-pr-review-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests manually makes it hard to see the full blast radius of a change, so reviewers miss callers outside the diff, untested flows, and breaking changes before merge. ## Core Features & Use Cases - Change Detection: Maps a PR diff to changed symbols and affected execution flows using gitnexus_detect_changes. - Blast Radius Analysis: Runs gitnexus_impact on each changed symbol to find d=1 callers that will break, including ones not updated in the PR. - Risk Assessment & Test Coverage: Classifies PRs as LOW/MEDIUM/HIGH/CRITICAL and checks which tests cover the changed code. - Use Case: When asked to review PR #42, the workflow fetches the diff, detects that validatePayment changed, finds webhookHandler calls it but was not updated, and flags the breakage in a structured review report. ## Quick Start Ask the assistant to review PR #42 and assess whether it is safe to merge using GitNexus impact analysis.

Frequently Asked Questions about gitnexus-pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for breaking changes?▼

Fetch the PR diff with gh pr diff, then run gitnexus_impact on each changed symbol with direction upstream. Any d=1 callers that exist outside the PR diff indicate potential breakage that should be flagged in the review.

How to check test coverage for a pull request?▼

Run gitnexus_impact with includeTests set to true on each changed symbol. It returns the tests that directly or indirectly cover the changed code, revealing untested execution flows affected by the PR.

What does the GitNexus index stale error mean during PR review?▼

A stale index means the code graph is out of date with the current source. Run npx gitnexus analyze in the terminal to rebuild the index before running detect_changes or impact queries.

How is pull request risk level assessed?▼

Risk is based on the number of changed symbols and affected processes: under 3 symbols is LOW, 3-10 is MEDIUM, more than 10 is HIGH, and changes touching auth, payments, or data integrity code are CRITICAL.

Can I use this review workflow without GitHub CLI?▼

The workflow uses gh pr diff to fetch the diff, but you can substitute git diff base...head to get the same changes. The GitNexus analysis steps work on any diff compared against a base ref like main.

Related Skills

Explore More Software Engineering Skills→
changfengprochangfengpro

gitnexus-pr-review

Reviews pull requests by mapping diffs to affected execution flows and blast radius.

Community
Intermediate
pbspbs
272

check-last-pr

Analyzes pull requests and recommends whether to merge, revise, or reject them.

Official
Advanced
opensage-agentopensage-agent
113

get-call-paths

Query a Neo4j graph database to identify call paths between source and destination functions.

Official
Advanced
ML4ITSML4ITS
165

gitnexus-refresh-on-stale

Refresh stale GitNexus indexes and sync local skills automatically.

Official
Basic