checking-what-my-github-prs-need-and-from-whomlisted
Install: claude install-skill sblattj/agent-chandlery
## More triggers
pr-activity-since-push, pr-approval-gate, checking-my-github-prs-for-activity-since-push, checking-what-blocks-my-github-prs-from-merging (old names), new reviews on my PRs, what's each PR waiting on, needs a code owner.
# What my GitHub PRs need, and from whom
## Do this
```bash
D=${CLAUDE_SKILL_DIR:-${SKILL_DIR:-~/.claude/skills/checking-what-my-github-prs-need-and-from-whom}}
$D/pr-activity.sh [owner/repo] # activity since your last push + CI + conflicts (non-draft PRs)
python3 -I $D/pr-approval-gate.py [-R owner/repo] # approvals, CODEOWNERS gaps, draft, behind (all open PRs)
```
- `pr-activity.sh`: repo is the arg, else the cwd repo, else `PR_ACTIVITY_REPO`. `AUTHOR=<login>` for someone else's PRs, `SINCE=<ISO8601>` to move the anchor. Needs bash 4+ (`mapfile`), `gh`, `jq`.
- `pr-approval-gate.py`: `-R owner/repo`, or a clone folder under `$PR_GATE_ROOT` (default `~/dev`), or the cwd's origin. `--author <login>`, `--pr <n> <m>`, `--json` for tooling. PR numbers need `--pr`: `pr-approval-gate.py 1750 1806` fails (the first number is read as the repo folder). About 15s for 23 PRs.
- Both are read-only and safe to run anytime. Run both for the full picture; run one when the question is only "did anyone respond" or only "who do I still need".
## Report: "Needs what from who"
Lead with one line on what awaits the user (review items, red CI, real conflicts), then one row per PR:
| PR | Blocked on | Who | Your move |
|----|---------