What problem does it solve? Writing pull request descriptions that accurately map every code change to its approved requirements is tedious and error-prone, and reviewers often cannot tell whether a change matches the agreed scope. This Skill automates that by reading the actual git diff against the base branch and producing a structured, ICEA-traceable PR description. ## Core Features & Use Cases - Diff-driven generation: Automatically resolves the base branch (Azure DevOps or GitHub), reads the git log and diff, and extracts the ADO work item ID from the branch name. - ICEA traceability: Maps every changed file to Acceptance Criteria, builds a scenario-coverage table, and flags scope creep when code exists without a matching requirement. - Reviewer-ready output: Produces a complete PR description with per-layer change summaries, test evidence, a Definition of Done checklist, and a self-review checklist. - Use Case: A developer finishes a feature branch, asks for a PR description, pastes the approved ICEA, and receives a complete description where each Acceptance Criterion links to the implementing file and each ICEA scenario links to its test. ## Quick Start Ask the assistant to write a PR description for your current branch and paste the approved ICEA for the linked ADO work item.
