pr-safetylisted

# PR Merge Safety Assessment Before merging a PR (especially to production), assess what could go wrong. This is NOT a code review — it's a risk assessment. **Input:** "$ARGUMENTS" ## Workflow ### 1. Identify the PR - If a PR URL or number is provided, use it - Otherwise detect from current branch: `gh pr view --json number,url,headRefName,baseRefName,state` - If the PR is closed or merged, stop ### 2. Understand the Change Gather context in parallel: ```bash # What files changed and how much gh pr diff <number> --name-only gh pr view <number> --json additions,deletions,changedFiles,title,body # Full diff gh pr diff <number> # What checks passed/failed gh pr checks <number> # Git history for changed files (is this area fragile?) gh api "repos/<owner>/<repo>/commits?path=<file>&per_page=10" \ --jq '.[] | "\(.sha[0:7]) \(.commit.author.date[0:10]) \(.commit.message | split("\n")[0][0:80])"' ``` Read the changed files in full (not just the diff) to understand the surrounding context. ### 3. Check for Related PRs Look for other open PRs that touch the same files or are part of the same initiative: ```bash # Other open PRs gh pr list --state open --json number,title,headRefName --limit 20 ``` If related PRs exist, note them — merging order may matter, or they may conflict. ### 4. Assess Risk Dimensions For each dimension, rate **LOW / MEDIUM / HIGH** with a one-line justification: **Blast Radius** - How many users/systems are affected? - Is this a hot path or