LowPR-scope Plug & play

Remove dead code and noisy diffs

Do not include commented-out code, unused files, or unrelated snapshots. Keep diffs minimal and relevant to the change.

Why this matters

Clean diffs improve focus, reduce repo bloat, and avoid confusion.

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

Avoid

// old impl kept for reference
// function oldDo() { ... }

Prefer

Removed obsolete helpers and snapshots not used by the new logic.

Bad

Commented blocks left in diff

Good

Separate gist/ADR for historical context; diff is minimal

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