pr-check

name	pr-check
description	Validate a PR against PR standards before requesting review
argument-hint	["pr-number"]

PR Standards Check

Pre-flight validation for PR quality.

Context

• Current branch: !git branch --show-current
• PR data: !gh pr view $ARGUMENTS --json title,body,additions,deletions,changedFiles,commits,baseRefName,number 2>/dev/null || echo "NO_PR_FOUND"
• Base branch: !gh pr view $ARGUMENTS --json baseRefName --jq .baseRefName 2>/dev/null || echo "main"
• Commits since base: !BASE="$(gh pr view $ARGUMENTS --json baseRefName --jq .baseRefName 2>/dev/null || echo main)"; git log --oneline "origin/$BASE..HEAD" 2>/dev/null || git log --oneline "$BASE..HEAD"

Instructions

Validate the current PR against each standard below. The base branch is baseRefName from the PR data (the branch the PR targets); it defaults to main when no PR exists. All "since base" comparisons below diff against this base, not a hardcoded main — so a stacked sub-PR targeting an integration branch is sized and scanned against that branch, not against main. If no PR number was provided and NO_PR_FOUND appears above, check only what can be validated locally (branch name, commits, diff size against the default base main) and note that no PR exists yet.

For each check, output one of:

• PASS — Meets the standard
• WARN — Minor deviation, note what's off
• FAIL — Does not meet the standard, explain what needs to change

Checks

1. Branch Naming Branch must match <type>/<short-description> where type is one of: feat, fix, refactor, docs, test, chore. Must be lowercase, hyphen-separated. No issue numbers in the branch name.

2. PR Title Must match <type>: <imperative summary>. Type prefix should match branch type. Under 72 characters. No period at the end. Imperative mood ("Add", "Fix"), not past tense ("Added", "Fixed").

3. PR Description — Summary Must include 1-3 sentences explaining what the change does and why.

4. PR Description — Test Evidence Must include how the change was verified: test output, manual steps, or "covered by existing tests."

5. PR Sizing Check additions + deletions (excluding generated code, test fixtures, lock files if identifiable):

• Under 400 lines → PASS
• 400-600 lines → WARN ("consider splitting")
• Over 600 lines → FAIL ("should be split")

6. Commit Messages Each commit message should follow <type>: <summary> format. No "WIP", "fixup", or "wip" commits.

7. References If the change relates to a GitHub issue, it should reference it with Closes #N or Relates to #N. WARN if no references found (not all PRs need them, but flag for awareness).

8. Secrets & Sensitive Data This project is open-source. The diff MUST NOT contain any of the following. FAIL immediately if found:

• API keys, tokens, or secrets — any string that looks like a bearer token, API key, bot token, OAuth secret, or password (check for patterns like sk-, ghp_, bot[0-9], xoxb-, Bearer , long hex/base64 strings assigned to credential variables). Tokens in test mocks/fixtures using obviously fake values are OK.
• Hardcoded user-specific paths — absolute paths referencing a specific user's home directory (e.g., /Users/alice/, /home/username/). Relative paths and ~/ are OK. Paths in CLAUDE.md, AGENTS.md, and documentation that describe the project setup are exempt.
• Real personal names or emails — real people's names, email addresses, phone numbers, or other PII in code or test fixtures. Synthetic/obviously fake data is OK (e.g., "John Doe", "[e-mail]"). Names in git commit metadata, CLAUDE.md, and AGENTS.md are exempt.
• Internal infrastructure details — Tailscale IPs, internal hostnames, or private network addresses in code (their presence in CLAUDE.md/AGENTS.md for developer setup is OK).

To check, read the full diff against the base branch: !BASE="$(gh pr view $ARGUMENTS --json baseRefName --jq .baseRefName 2>/dev/null || echo main)"; git diff "origin/$BASE..HEAD" -- ':!CLAUDE.md' ':!AGENTS.md' 2>/dev/null || git diff "$BASE..HEAD" -- ':!CLAUDE.md' ':!AGENTS.md'

Output Format

## PR Standards Check

| # | Check | Result | Notes |
|---|-------|--------|-------|
| 1 | Branch naming | PASS/WARN/FAIL | ... |
| 2 | PR title | PASS/WARN/FAIL | ... |
| 3 | Summary | PASS/WARN/FAIL | ... |
| 4 | Test evidence | PASS/WARN/FAIL | ... |
| 5 | Sizing | PASS/WARN/FAIL | ... |
| 6 | Commit messages | PASS/WARN/FAIL | ... |
| 7 | References | PASS/WARN/FAIL | ... |
| 8 | Secrets & sensitive data | PASS/WARN/FAIL | ... |

**Result: X/8 passing, Y warnings, Z failures**

If there are failures, add a brief "Suggested Fixes" section listing what to change.