review-issue-implementation

To validate code changes against issue cards, provide the ISSUE_PATH and EXECPLAN_PATH to initiate a review. The skill analyzes git diffs against documented requirements to ensure coverage and flag divergences.

Mapping requirements to a git diff works by cross-referencing AGENTS.md and PLANS.md artifacts with code changes. It matches each requirement from the issue card to corresponding modifications, flagging gaps or divergences.

The best way to check if staged changes align with PLANS.md requirements is to run a review using the STAGED diff range. The skill loads governing documents and generates prioritized findings with file paths and line references.

Yes, you need AGENTS.md and PLANS.md files to perform a diff-based code review. These repository governance artifacts provide the explicit requirements used to map changes and assess compliance.

Yes, you can use the WORKING_TREE diff range for requirements mapping and risk assessment. The skill analyzes uncommitted changes against issue cards and produces a concise change summary with a regression overview.

A limitation when analyzing git diffs for ExecPlan coverage is that the review relies entirely on AGENTS.md and PLANS.md. The skill cannot validate requirements that are missing or undocumented within these governance artifacts.