ah-verify-requirements-coverage

To verify pull request coverage, the Skill analyzes the diff between PR changes and linked GitHub issue requirements, mapping each requirement to code changes and computing a coverage percentage. It generates a structured per-issue report detailing fully, partially, or not covered items.

Yes, you can check local branch changes against GitHub issue requirements. The Skill supports remote PRs and local branch work, automatically extracting issue references from PR bodies or branch names to compute requirement coverage.

Requirements coverage mapping works by analyzing the diff between code changes and the explicit requirements in a linked GitHub issue. It maps each requirement to concrete code modifications, calculates a coverage percentage, and identifies gaps with actionable next steps.

The best way to prevent incomplete PR changes is to validate that every requirement from a linked issue is addressed by the diff. This manages regression and scope creep risks by generating a coverage report with clear statuses for each requirement.

Yes, this requirements verification tool works directly with GitHub pull requests. It extracts linked issues from PR bodies, analyzes the code diff against those issue requirements, and produces a structured coverage report.

A requirements coverage report includes per-issue statuses showing whether requirements are fully covered, partially covered, or not covered. For any gaps found, it provides actionable next steps to achieve full requirement coverage.