skills.rest
abhigyanpatwari
abhigyanpatwariCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-pr-review

Map pull request diffs to affected execution flows and risks.

45.2k|5.0k|Updated Aug 2, 2025
Search Tags:#git#context#github#code-review#blast-radius#risk-analysis#pr-review
One-click install
npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-pr-review-abhigyanpatwari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/abhigyanpatwari/GitNexus/tree/main/gitnexus-cursor-integration/skills/gitnexus-pr-review
Command: npx skills add https://github.com/abhigyanpatwari/GitNexus --skill gitnexus-pr-review-abhigyanpatwari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews of pull requests can be lengthy and hard to track, making it easy to miss how changes affect the system. GitNexus-pr-review provides a structured, guided workflow that maps PR changes to affected execution flows and risks, helping reviewers make informed decisions quickly.

Core Features & Use Cases

  • Diff-to-flow mapping: convert PR diffs into affected execution flows and symbol impact.
  • Risk & test visibility: assess blast radius, upstream dependencies, and test coverage gaps.
  • Contextual reasoning: surface callers/callees and processes that may be affected to guide reviews.

Quick Start

Review a PR by diffing the pull request and summarizing the blast radius with context from GitNexus.

Frequently Asked Questions about gitnexus-pr-review

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

FAQPage Schema
What is blast radius analysis in a PR review?▼

Blast radius analysis in a PR review identifies the potential impact of code changes by mapping modified symbols to affected execution flows. It surfaces callers, callees, and processes impacted by the diff.

How do I assess merge risks and missing tests for a GitHub PR?▼

Assess merge risks and missing tests by mapping PR diffs to impacted execution flows. This surfaces test coverage gaps and upstream dependencies, generating a concise risk assessment to guide merge decisions.

Do I need the gh CLI to analyze pull request diffs?▼

Yes, you need the gh CLI to fetch pull request diffs. The review workflow reads the current PR diff via gh CLI to map changed symbols and generate a concise risk assessment.

Can I map PR diffs to affected execution flows automatically?▼

Yes, PR diffs can be mapped to affected execution flows automatically. Workflows detect changed symbols and surface impacted callers and callees to provide contextual reasoning for code reviews.

What is the best way to find test coverage gaps in a code review?▼

The best way to find test coverage gaps in a code review is to map PR changes to impacted execution flows. This assesses the blast radius and explicitly highlights missing tests for changed symbols.

When should I not use automated risk analysis for pull requests?▼

Automated risk analysis for pull requests is not suitable when you lack the gh CLI to fetch diffs, or when changes are completely isolated with no existing execution flows, callers, or callees to map.

Related Skills

Explore More Software Engineering Skills→
xlelibertyxleliberty

pr-review-expert

Analyze GitHub and GitLab pull request diffs for security and breaking changes.

Community
Advanced
gerald-icagerald-ica

gitnexus-pr-review

Map pull request changes to execution flows and assess merge risk.

Community
Advanced
nathanvalenathanvale
2

index-graph-navigator

Query a codebase call graph for blast radius and dead code analysis.

Community
Intermediate
anukkrit149anukkrit149

gitnexus-pr-review

Detect code changes in pull requests and map them to affected execution flows and symbols.

Community
Advanced