skills.rest
shysssthanhtri
shysssthanhtriCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-pr-review

Assess pull request changes and summarize risk and impact on execution flows.

Updated Mar 19, 2026
Search Tags:#code review#pr review#test coverage#risk assessment#blast radius#gitnexus
One-click install
npx skills add https://github.com/shysssthanhtri/AI-tools --skill gitnexus-pr-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/gitnexus-pr-review
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill gitnexus-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps reviewers rapidly understand what a pull request changes, which runtime flows and callers those changes affect, whether tests cover the change, and whether merging introduces breakage or high-risk behavior.

Core Features & Use Cases

  • Map a PR diff to specific changed symbols and the execution flows they touch to focus review effort.
  • Compute blast radius per symbol to identify d=1/d=2 dependents and surface potential breaking callers.
  • Highlight missing or insufficient test coverage and surface callers that are outside the PR diff.
  • Produce a concise risk-rated review summary with findings and actionable recommendations for approve/request changes decisions.

Quick Start

Review PR #42 and produce a risk-rated summary listing changed symbols, affected execution flows, missing tests, and recommended actions.

Frequently Asked Questions about gitnexus-pr-review

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

FAQPage Schema
How do I assess pull request risk and blast radius during code review?▼

To assess pull request risk, map the PR diff to changed symbols and compute blast radius to identify d=1/d=2 dependents. This surfaces affected execution flows and potential breaking callers to focus review effort.

How does blast radius analysis identify breaking callers in a PR?▼

Blast radius analysis maps changed symbols to their d=1 and d=2 dependents. This identifies execution flows and callers outside the PR diff that might break, highlighting potential regressions.

How do I check test coverage for changed symbols in a pull request?▼

Check test coverage by mapping changed symbols to existing tests using a code index. This highlights missing or insufficient test coverage and surfaces callers outside the PR diff.

What do I need to generate a risk-rated PR review summary?▼

You need PR diffs and a code index or analysis tool to map changed symbols. The summary lists affected execution flows, missing tests, and actionable recommendations for approve or request changes decisions.

Can I review PR execution flows without a code analysis tool?▼

No, mapping changed symbols to callers and tests requires a code index or analysis tool. Without it, you cannot compute blast radius or check test coverage for affected execution flows.

When do I need symbol-level mapping for code review?▼

You need symbol-level mapping when a PR modifies core functions and you must understand execution flows. It computes blast radius to surface breaking callers and missing tests before merging.

Related Skills

Explore More Software Engineering Skills→
wutongshenqiuwutongshenqiu

gitnexus-refactoring

Map code symbol dependents to determine refactoring blast radius.

Community
Advanced
wshaddixwshaddix
71

crap-analysis

Analyze .NET code for CRAP scores and generate coverage reports.

Community
Intermediate
guideopsguideops

gitnexus-pr-review

Analyzes pull requests for impact, risk, and test coverage.

Community
Advanced
nassimbfnassimbf
3

canary-watch

Monitor a deployed URL for HTTP status, console errors, performance metrics, and content changes.

Community
Intermediate