gitnexus-pr-review

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

Updated May 26, 2026

Search Tags:#GitHub #impact analysis #test coverage #risk assessment #dependency graph #pull request review #GitNexus

Ready to run

npx skills add https://github.com/anukkrit149/anukkrit-skills --skill gitnexus-pr-review-anukkrit149

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/anukkrit149/anukkrit-skills/tree/main/cloud/skills/gitnexus-pr-review
Command: npx skills add https://github.com/anukkrit149/anukkrit-skills --skill gitnexus-pr-review-anukkrit149

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand what a pull request changes, how risky it is to merge, and whether the change is missing test coverage.

Core Features & Use Cases

PR diff to affected flows: Uses GitNexus change detection to map the PR diff to execution processes and impacted symbols.
Blast radius assessment: Quantifies upstream dependency impact (including potential breakage from d=1 items).
Coverage and review output: Recommends approve/request changes by identifying missing test coverage and summarizing findings in a consistent format.
Use Case: You receive a PR that touches core business logic and want to verify correctness, blast radius, and whether enough tests exist before merging.

Quick Start

Ask the AI to review PR changes for a specific PR number and summarize risk, missing test coverage, and merge recommendations using GitNexus.

Frequently Asked Questions about gitnexus-pr-review

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

FAQPage Schema

How do I analyze pull request risk and missing test coverage before merging?▼

Pull request risk analysis maps code changes to affected execution flows and symbols to quantify blast radius, verify correctness, and identify missing test coverage. It uses GitNexus change detection to evaluate production repository PRs and outputs structured merge recommendations.

What is blast radius analysis for a GitHub pull request?▼

Blast radius analysis for a GitHub pull request quantifies the upstream dependency impact of code changes, including potential breakage from direct dependencies. It maps modified symbols to their execution processes to assess the overall risk of merging the PR.

How do I review a GitHub PR using a dependency graph?▼

Reviewing a GitHub PR with a dependency graph involves retrieving the diff and mapping the changed code to impacted symbols and processes. This impact analysis evaluates downstream effects and missing test coverage to generate a risk level and merge recommendation.

Does PR risk assessment work with existing GitHub workflows?▼

Yes, PR risk assessment integrates with existing GitHub workflows by using gh-based diff retrieval to fetch pull request changes. It then applies GitNexus change detection tools to map the diff to affected flows and output a structured review.

When should I use automated impact analysis for pull requests?▼

Automated impact analysis for pull requests should be used when a PR touches core business logic in production repositories. It helps verify correctness, assess blast radius, and determine whether enough tests exist before merging high-risk code changes.