gxpm-review-changes

Map diffs to affected symbols and execution flows for code review risk analysis.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/laozhong86/gxpm --skill gxpm-review-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gxpm-review-changes
Source: https://github.com/laozhong86/gxpm/tree/main/skills/gxpm-review-changes
Command: npx skills add https://github.com/laozhong86/gxpm --skill gxpm-review-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates risk-aware evaluation of code changes by mapping diffs to execution symbols and highlighting high-impact changes to inform merge decisions.

Core Features & Use Cases

  • Maps diffs to affected symbols and execution flows to surface risk areas during code reviews.
  • Performs impact analysis with context to callers and callees, aiding informed decision-making.
  • Produces a structured review findings record for PR checks, self-review, and gatekeeping the release process.

Quick Start

Invoke the skill during the PR review to map diffs to symbols and surface high-risk changes for a structured findings record.

Frequently Asked Questions about gxpm-review-changes

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

FAQPage Schema
How do I perform risk-aware code review on pull requests?

Risk-aware code review maps diffs to affected symbols and execution flows to highlight high-impact changes. This process surfaces risk areas during PR reviews, ensuring informed merge decisions based on actual execution impact.

What is diff analysis in the context of PR checks?

Diff analysis identifies modified code segments and connects them to affected symbols and execution flows. It provides context to callers and callees, producing a structured findings record to gatekeep the release process.

How do I map code diffs to execution flows for impact analysis?

Mapping code diffs to execution flows involves tracing modified symbols to their callers and callees. This impact analysis highlights risk areas with context, verifying test coverage and generating actionable recommendations for merge decisions.

Can I integrate PR review findings into an artifact lifecycle?

Yes, structured PR review findings integrate with the artifact lifecycle to inform merge decisions. The skill produces a findings record containing context, impact analysis, and actionable recommendations during the release process.

What is the best way to verify test coverage after code changes?

Verifying test coverage after code changes requires mapping diffs to affected execution flows to highlight risk areas. This risk assessment produces a structured findings record that aids self-review and gatekeeping before merging.

When should I use automated risk analysis for code review?

Automated risk analysis should be used during PR reviews, risk assessment before merging, and verification of test coverage after changes. It automates evaluation by mapping diffs to execution symbols to highlight high-impact changes.