gitnexus-pr-review

Map pull request code diffs to affected execution flows and assess merge risk.

15|2|Updated May 23, 2026
One-click install
npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill gitnexus-pr-review-vkirill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/VKirill/antigravity-for-claude-code/tree/main/skills/gitnexus-pr-review
Command: npx skills add https://github.com/VKirill/antigravity-for-claude-code --skill gitnexus-pr-review-vkirill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand what a pull request changes and how risky it is to merge by mapping code changes to affected execution flows, likely breakpoints, and test coverage gaps.

Core Features & Use Cases

  • PR change-to-flow mapping: Detects changed symbols from a PR diff and identifies the execution flows impacted across the system.
  • Blast-radius impact analysis: Computes upstream dependencies (including WILL BREAK signals) and quantifies risk based on how far changes propagate.
  • Context-aware review and verification: Pulls caller/callee context for changed symbols and checks whether affected areas have adequate test coverage.
  • Use cases: Reviewing someone else’s PR, assessing merge safety, answering “what’s the blast radius,” and identifying missing tests before integrating changes.

Quick Start

Ask for a PR review by telling the assistant which PR number you want reviewed (for example, “Review this PR #42 and assess merge risk with missing test coverage.”).

Frequently Asked Questions about gitnexus-pr-review

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

FAQPage Schema
How do I determine the blast radius of a pull request before merging?

A pull request blast-radius analysis maps code diffs to affected execution flows and upstream dependencies. It computes WILL BREAK signals and quantifies merge risk by evaluating how far changed symbols propagate across the system before integration.

What is the best way to check test coverage for changed symbols in a GitHub PR?

Checking test coverage for a GitHub PR involves pulling caller and callee context for changed symbols. The review identifies affected execution flows and flags missing test coverage in those specific areas to verify merge safety.

How do I review a GitHub pull request for breaking changes and dependency impact?

Reviewing a GitHub pull request for breaking changes requires fetching the PR diff and running impact analysis on changed symbols. This detects dependency impact and upstream WILL BREAK signals to assess merge safety before integrating code.

Can I identify missing tests in affected execution flows when reviewing a PR?

Yes, you can identify missing tests in affected execution flows during a PR review. The process maps code changes to impacted execution flows and checks whether those specific affected areas have adequate test coverage before merging.

Does pull request impact analysis require fetching the complete diff?

Yes, pull request impact analysis requires fetching the PR diff. The diff is processed to detect changed symbols, which are then analyzed to compute upstream dependency impact and assess overall merge risk.