merge-follow-uplisted
Install: claude install-skill SeanoChang/seanock
# merge-follow-up
After a merge, the same steps follow each time: fetch, rebase the branches
that are now behind, reinstall, go on. This skill lets a session see the
merge itself and do those steps, so the user does not have to type "merged".
This skill never merges a pull request. A task pull request is merged by the
rules in `CLAUDE.md` (review, CI, the merge gate). A release pull request is
merged by the user.
## 1. Look
Run this from anywhere, as its own command, with no pipe:
```bash
python3 ~/.claude/skills/merge-follow-up/scripts/pr-state.py --repo <project root>
```
The script reads the pull requests of the signed-in GitHub user with `gh`.
It changes nothing on GitHub and nothing in git. A session's first look
records what is there and reports nothing; each later look reports what
changed since the look before.
A Claude Code session is named by itself. Any other caller (Codex, a script)
adds `--session <a fixed name>` and uses the same name each time.
Read the exit code and the last line together:
| Exit | Last line | Meaning |
| --- | --- | --- |
| 0 | `pr-state: clean` | Nothing changed. |
| 1 | `pr-state: summary events=N` | N events, one JSON object on each line above. |
| 2 | `pr-state: error ...` | It could not finish. This says nothing about the pull requests. |
Anything else is not a result. Never read a failed look as "nothing changed".
## 2. When to look
- **Right after you open a pull request that waits for the user.** This is
the first look.