pull-request-quality-contract

Validates pull request evidence against repository definition-of-done and PR template requirements.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill pull-request-quality-contract-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request-quality-contract
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/.agents/skills/pull-request-quality-contract
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill pull-request-quality-contract-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pull-request-quality-contract

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

FAQPage Schema
How do I write a pull request with proper verification evidence?

Run this Skill before opening the PR. It reads your repository's definition of done and PR template, maps each behavior change to tests or screenshots, runs relevant checks, and writes the PR body with Why, What changed, Behavioural Proof, and Verification Summary sections.

What proof is required for UI changes in a pull request?

User interface changes require current screenshots or video captured from the branch under review. If visual proof does not apply, the PR must state Not applicable with a technical reason rather than omitting the section.

Can I skip tests or checks in a pull request?

Yes, but only with an explicit technical reason, the associated risk, and a follow-up owner named in the PR. Skipping proof for convenience is not accepted, and existing unrelated failures must be separated from failures introduced by the PR.

Does this replace CI checks or repository validators?

No. It does not replace the repository validator or continuous integration, and it will not mark a PR ready while relevant checks are still failing, queued, or running. It only ensures the documented evidence is complete and honest.

When is screenshot or video proof not required?

Non-visual changes such as documentation, governance, or script-only updates do not require screenshots or video. The PR should state Not applicable with the reason in the Behavioural Proof section.