skills.rest
gerald-ica
gerald-icaCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-pr-review

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

Updated Apr 14, 2026
Search Tags:#workflow#diff#code-review#risk#pr-review#impact#gitnexus
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill gitnexus-pr-review-gerald-ica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-pr-review
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/gitnexus-pr-review
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill gitnexus-pr-review-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and teams quickly understand PR changes, assess risk of merging, and verify test coverage to ensure safe integrations.

Core Features & Use Cases

  • Map PR diffs to affected execution flows and symbol dependencies.
  • Assess blast radius and overall merge risk across modified components.
  • Review callers/callees and test coverage to ensure changes are properly validated.

Quick Start

Review this PR and generate a risk-aware summary using the GitNexus PR Review workflow.

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 the blast radius of a pull request before merging?▼

To assess the blast radius of a pull request, map PR diffs to affected execution flows and symbol dependencies to determine overall merge risk across modified components.

What is the best way to trace execution flow impact from a code review diff?▼

Tracing execution flow impact during code review involves mapping PR diffs to affected symbol dependencies and reviewing callers and downstream processes to verify changes.

How do I generate a risk-aware summary for a PR review?▼

Generate a risk-aware PR review summary by detecting changes with GitNexus tools, determining blast radius, tracing caller impacts, and verifying test coverage across modified symbols.

Can I verify test coverage for modified symbols during a PR review?▼

Yes, you can verify test coverage for modified symbols during a PR review by tracing impacts, reviewing callees, and checking test validation across the affected execution flows.

Why should I map PR diffs to affected execution flows?▼

Mapping PR diffs to affected execution flows identifies hidden symbol dependencies and downstream process impacts, ensuring changes are properly validated and safe for integration.

Related Skills

Explore More Software Engineering Skills→
s1366560s1366560
5

gitnexus-impact-analysis

Analyze code change impact by mapping upstream dependencies and affected execution flows.

Community
Intermediate
finlaysonstudiofinlaysonstudio
2

shepherd

Automate end-to-end merge workflows from feature branches to deployment.

Official
Advanced
AlbertLin821AlbertLin821
2

gitnexus-pr-review

Analyze pull request diffs to map code changes to affected execution flows.

Community
Advanced
handbrianchandbrianc

gitnexus-exploring

Navigate and analyze codebase architecture, execution flows, and symbol dependencies with GitNexus.

Community
Intermediate