skills.rest
changfengpro
changfengproCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitnexus-pr-review

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

Updated May 28, 2026
Search Tags:#code review#pull request#github#impact analysis#test coverage#blast radius#gitnexus
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill gitnexus-pr-review-changfengpro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/gitnexus-pr-review
Command: npx skills add https://github.com/changfengpro/agent-skills --skill gitnexus-pr-review-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests manually makes it hard to see which callers, execution flows, and tests are affected by a change, so breaking changes and missing test coverage slip through review. ## 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 if not updated. - Test Coverage Check: Uses gitnexus_impact with includeTests to identify which tests cover changed code and which flows are untested. - Use Case: When asked "Is PR #42 safe to merge?", the Skill fetches the diff, detects that webhookHandler calls a changed function but is not updated in the PR, and produces a structured review with a MEDIUM risk rating and a REQUEST CHANGES recommendation. ## Quick Start Ask the assistant to review PR #42 and assess whether it is safe to merge.

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_detect_changes to map changes to affected flows. Run gitnexus_impact on each changed symbol to find d=1 callers that will break if they are not updated in the PR.

How to check test coverage for a pull request?▼

Run gitnexus_impact with includeTests set to true on each changed symbol. It lists the tests that directly or indirectly cover the changed code, revealing flows that lack test coverage.

What is the blast radius of a code change?▼

Blast radius is the set of callers and execution flows affected by a change. gitnexus_impact shows d=1 items that will break, d=2 items likely affected, and d=3 downstream dependents for any target symbol.

Why does the review say the GitNexus index is stale?▼

A stale index means the code graph does not reflect the latest commits. Run npx gitnexus analyze in the terminal to rebuild the index before performing the review.

When is a pull request considered high risk to merge?▼

Risk is HIGH when changes touch more than 10 symbols or many processes, and CRITICAL when they touch auth, payments, or data integrity code. d=1 callers outside the PR diff also signal potential breakage.

Related Skills

Explore More Software Engineering Skills→
AlbertLin821AlbertLin821
2

gitnexus-pr-review

Analyze pull request diffs to map code changes to affected execution flows.

Community
Advanced
xtrm-devxtrm-dev
4

gitnexus-pr-review

Map PR diffs to execution flows and identify merge risks.

Official
Intermediate
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate
juicesharpjuicesharp
581

code-review

Orchestrate multi-agent code review workflows to generate structured review documents from patch diffs.

Community
Advanced