HighPR-scope Plug & play

Include testing evidence or steps-to-reproduce

Provide explicit verification steps (manual or automated), expected vs actual outcomes, and attach any logs or screenshots relevant to the changes.

Why this matters

Reproducible verification accelerates review and catch regressions.

Side-by-side examples engineers can pattern-match during review.

Avoid

Tests pass locally.

Prefer

Steps:
1) Start service
2) Call /v1/quote with payload X
Expected: 200 w/ field Y
Actual before: 500; after: 200
Screenshot/log attached.

Bad

Trust me, it works

Good

Steps + expected/actual

From the same buckets as this rule.

High
Avoid mixed concerns in one PR
Do not combine mechanical changes (formatting, renames) with behavioral changes. If unavoidable, separate commits and call out which commits are mechanical.
pr-hygienereadability-refactor+1
High
Behavioral changes must add or update tests
If files under src/ change behavior, the PR must include tests/ updates or a PR description line no-tests: <reason> explaining why tests are unaffected.
testing-qualitypr-hygiene
High
Bugfix PRs must match the real production failure (root cause, not band-aid)
If the PR claims to fix a specific issue (e.g., 'Fixes #123' / 'Fix PAY-123'), validate it against the real production error. - If an observability MCP is available (Sentry/Datadog/Bugsnag): fetch the event/stack trace and confirm the change addresses the root cause. - Require a regression test (or a clearly documented reason why a test cannot be added). Call out fixes that only hide symptoms (catch-and-ignore, broader retries, defaulting values) without removing the underlying failure mode.
pr-hygieneerror-handling+2