| name | pr-standards |
| description | Use when creating, reviewing, or preparing a pull request — enforces team PR standards including size, summary quality, CI checks, commit hygiene, and review workflow. |
| metadata | {"author":"Azure"} |
Pull Request Standards
All PR rules are maintained in a single source of truth. Read and enforce every rule in:
CONTRIBUTING.md — Pull Request Standards
Do not duplicate the rules here. Always read CONTRIBUTING.md before creating or reviewing a PR.
The PR checklist is built into .github/PULL_REQUEST_TEMPLATE.md — it appears automatically on every new PR.
Workflow
When the user asks to create a PR:
- Read rules: Open
CONTRIBUTING.md and read the "Pull Request Standards" section in full.
- Pre-flight: Run
git diff and review changes. Flag anything that violates the rules.
- Scope check: If the diff touches unrelated concerns, recommend splitting into separate PRs.
- Generate description: Write a summary following the rules, include ticket links. The checklist is auto-populated by the PR template.
- Title: Use Conventional Commits format (
feat:, fix:, docs:, etc.).
- CI check: Run available tests/linting and report status. Ignore Tide — it is not a CI check.
- Draft vs. Ready: Ask whether to open as Draft if work appears incomplete.
- Reviewers: Suggest specific reviewers based on file ownership (CODEOWNERS, git blame).
Source: Azure/ARO-HCP — distributed by TomeVault.
