skills.rest
gmolike
gmolikeCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-pr-review

Reviews pull requests using GitNexus code graph analysis to assess blast radius and merge risk.

Updated Mar 4, 2026
Search Tags:#code review#pull request#github#impact analysis#blast radius#gitnexus#merge risk
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-pr-review-gmolike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/gitnexus-pr-review
Command: npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-pr-review-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests by reading raw diffs alone misses how changes ripple through callers, execution flows, and test coverage, leading to undetected breaking changes and unsafe merges. ## Core Features & Use Cases - Index Freshness Verification: Compares the GitNexus indexed commit against HEAD before reviewing, preventing stale-graph false approvals. - Blast Radius Analysis: Maps each changed symbol to upstream dependents (d=1/d=2/d=3) via gitnexus_impact to find callers not updated in the PR. - Flow and Coverage Mapping: Uses gitnexus_detect_changes and gitnexus_context to identify affected execution flows and missing test coverage. - Use Case: When asked to review PR #42, the skill fetches the diff, maps changed symbols to CheckoutFlow and RefundFlow, flags a webhookHandler caller that was not updated, and outputs a structured risk-rated review with an APPROVE or REQUEST CHANGES recommendation. ## Quick Start Ask the assistant to review a specific pull request, for example: Review PR #42 and tell me if 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_impact on each changed symbol to list upstream callers. Any d=1 dependent not updated in the PR diff is a potential breaking change that should be flagged in the review.

How to check the blast radius of a code change before merging?▼

Use gitnexus_impact with direction upstream on the changed symbol to see d=1, d=2, and d=3 dependents. Combine this with gitnexus_detect_changes to see which execution flows the change touches and assign a LOW to CRITICAL risk level.

Why does gitnexus_detect_changes report no changes on a non-empty diff?▼

This means the GitNexus index is stale, not that the PR is safe. The tool never checks staleness, so compare the indexed commit from npx gitnexus status against git rev-parse HEAD and run npx gitnexus analyze if they differ.

Can I check test coverage for changed code in a PR?▼

Yes, call gitnexus_impact with includeTests set to true on the changed symbol. It returns the tests that directly or indirectly cover that code, letting you identify affected flows that lack test coverage.

What does risk UNKNOWN mean in gitnexus_impact results?▼

UNKNOWN with a not found error means the symbol was never indexed, typically because the PR adds new symbols to a stale index. Treat it as a signal to re-index, never as evidence of low risk.

Related Skills

Explore More Software Engineering Skills→
ibytechaosibytechaos
1

gitnexus-pr-review

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

Community
Intermediate
2460124601

ship

Merge base branch, run tests, bump VERSION, update CHANGELOG, and open a pull request.

Community
Advanced
alangebalangeb

code-review-workflow

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

Community
Intermediate
AI-Foundry-CoreAI-Foundry-Core
4

helm-chart-scaffolding

Scaffold Helm charts with Chart.yaml, values.yaml, and templates.

Official
Advanced