enforcing-pr-contract

Enforce three PR contract checks on board-superpowers card submissions.

2|Updated Apr 24, 2026

Search Tags:#automation #workflow #github #validation #pull-request #pr-contract

Ready to run

npx skills add https://github.com/PanQiWei/board-superpowers --skill enforcing-pr-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enforcing-pr-contract
Source: https://github.com/PanQiWei/board-superpowers/tree/main/skills/enforcing-pr-contract
Command: npx skills add https://github.com/PanQiWei/board-superpowers --skill enforcing-pr-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforcing PR contracts ensures PR bodies, linked card acceptance criteria, and auto-close linkage are present and non-filler, preventing rush merges and misaligned work in board-superpowers workflows.

Core Features & Use Cases

Enforces Contract A: PR body structure with non-filler content.
Enforces Contract B: Linked card acceptance criteria are in terminal state before PR submission.
Enforces Contract C: PR body contains auto-close keywords referencing the linked card at PR open time.
Applies on both the Consumer side during PR submission and the Producer side during review-queue triage.
Supports an override via the pr-contract-override label for supervised bypass.

Quick Start

Draft the PR body for the claim branch and run the submit-pr.sh flow to apply Contract A, Contract B, and Contract C at PR-open time.

Frequently Asked Questions about enforcing-pr-contract

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

FAQPage Schema

How do I enforce pull request validation checks to prevent skipped reviews?▼

To enforce pull request validation, you can implement a three-contract PR discipline that verifies PR body structure, linked card acceptance criteria, and auto-close keywords to prevent rush merges in GitHub workflows.

What is a PR contract and how does it stop misaligned merges?▼

A PR contract is a validation rule ensuring PR bodies contain non-filler content, linked card acceptance criteria are in a terminal state, and auto-close linkage references the card, stopping misaligned merges before code integration.

How do I automate GitHub PR checks for required body content and linked cards?▼

You can automate GitHub PR checks by running the submit-pr.sh flow at PR-open time, which validates non-empty body sections, checks terminal acceptance criteria, and injects auto-close keywords referencing the linked card.

Can I bypass PR contract validation for specific pull requests?▼

Yes, you can bypass PR contract validation for specific pull requests by applying the pr-contract-override label, which allows a supervised bypass of the three contract checks during submission or review.

Does PR contract enforcement work for both drafting and reviewing workflows?▼

PR contract enforcement applies across both consumer submission flows during PR drafting and producer review workflows during triage, validating PR body structure and linked card acceptance criteria on both sides.

Why does my pull request validation fail when acceptance criteria are not finished?▼

Pull request validation fails because Contract B requires the linked card acceptance criteria to reach a terminal state before PR submission, ensuring work is fully completed and verified before merging.