What problem does it solve? Pull requests often ship with vague descriptions, missing test evidence, or skipped checks that reviewers cannot verify. This Skill enforces a concrete evidence contract before work is marked complete, ensuring every PR states why the change exists, what changed, and what proof backs it. ## Core Features & Use Cases - Evidence Mapping: Reads .agents/DEFINITION_OF_DONE.md and .github/pull_request_template.md, then maps each behavior change to the smallest relevant proof such as tests, command output, screenshots, or video. - Structured PR Body Generation: Writes or updates the pull request body using the repository template with the exact sections Why does this feature exist?, What changed?, Behavioural Proof, and Verification Summary. - Skipped-Check Accountability: Requires any skipped verification to name a technical reason, risk, and follow-up owner rather than a convenience excuse. - Use Case: Before opening a PR that changes a checkout flow, run this Skill to confirm end-to-end tests cover the new behavior, attach branch screenshots, run lint and type checks, and produce a complete PR body. ## Quick Start Run /pull-request-quality-contract before opening my pull request to verify all proof and checks are documented.