skills.rest
xtrm-dev
xtrm-devOFFICIAL
Explore all skills by this author →
GitHub

gitnexus-pr-review

Map PR diffs to execution flows and identify merge risks.

4|1|Updated Nov 1, 2025
Search Tags:#code review#pull request#impact analysis#test coverage#blast radius#merge risk
One-click install
npx skills add https://github.com/xtrm-dev/specialists --skill gitnexus-pr-review-xtrm-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/xtrm-dev/specialists/tree/main/.xtrm/skills/default/gitnexus-pr-review
Command: npx skills add https://github.com/xtrm-dev/specialists --skill gitnexus-pr-review-xtrm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review pull requests faster by showing what changed, what those changes affect, and whether the merge is likely to break anything important.

Core Features & Use Cases

  • Change Impact Mapping: Connects PR diffs to affected execution flows and changed symbols.
  • Risk Assessment: Flags breaking callers, likely regressions, and higher-risk areas before merge.
  • Test Coverage Review: Checks whether impacted code paths and dependencies have meaningful test coverage.
  • Use Case: Use it when you need to review a teammate’s PR, decide if it is safe to merge, or explain the blast radius of a code change.

Quick Start

Ask the Skill to review a specific pull request and summarize the changes, risks, missing coverage, and merge recommendation.

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 pull request code review?▼

Blast radius analysis maps changed code symbols to affected execution flows and upstream or downstream dependencies, identifying breaking callers and likely regressions before a pull request merge.

How do I check merge risk and missing test coverage for a PR diff?▼

Trace PR diff changes across execution flows to flag breaking callers, assess merge risk, and identify impacted code paths lacking meaningful test coverage to produce a risk-rated merge recommendation.

How do I analyze change impact across upstream and downstream dependencies before merging?▼

Map PR diffs to affected execution flows, trace upstream and downstream dependencies, and flag breaking callers to document a risk-rated review highlighting coverage gaps before merging.

Does this code review skill work without external dependencies?▼

The code review skill operates without external dependencies, requiring only PR diff access and GitNexus change detection to trace impact, assess merge risk, and document coverage gaps.

What is the best way to identify breaking callers in a code review?▼

Map changed symbols to affected execution flows, check upstream and downstream dependencies, and flag likely regressions during impact analysis to identify breaking callers before merging.

When should I not use automated impact analysis for a pull request?▼

Avoid automated impact analysis when PR diff access is unavailable, as the review requires diff access and GitNexus change detection to trace affected execution flows, assess merge risk, and document coverage gaps.

Related Skills

Explore More Software Engineering Skills→
xtrm-devxtrm-dev
4

gitnexus-impact-analysis

Analyze code change impact on dependent symbols and execution flows.

Official
Intermediate
anukkrit149anukkrit149

gitnexus-pr-review

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

Community
Advanced
erikhazzarderikhazzard
1

testing--auditing

Audit automated test suites for coverage gaps, oracle strength, and determinism.

Community
Advanced
vTRKAvTRKA

code-search

Search codebases via CodeGraph queries for symbols, callers, and dependencies.

Community
Advanced