setup-repolisted
Install: claude install-skill SeanoChang/seanock
# setup-repo
The rules in `CLAUDE.md` assume things about a repo: a branch that takes the
task pull requests, CI that the merge gate can read, a map that names the
commands, a file that names the risky paths. In a repo that lacks one of
them, a rule has nothing to hold on to. This skill finds what is missing and
fills it.
This skill never merges a pull request. A task pull request is merged by the
rules in `CLAUDE.md` (review, CI, the merge gate).
## 1. Look
Run `git fetch origin` first: the branch check reads what the last fetch
saw, not GitHub. Then run this, as its own command, with no pipe:
```bash
python3 ~/.claude/skills/setup-repo/scripts/repo-doctor.py --repo <project root>
```
The script only reads. It writes no file, and it calls no network and no
`gh`. Read the exit code and the last line together:
| Exit | Last line | Meaning |
| --- | --- | --- |
| 0 | `repo-doctor: clean` | Every check is `ok`. |
| 1 | `repo-doctor: summary gaps=N unknown=M` | One line for each check above, and N of them are a gap. |
| 2 | `repo-doctor: error ...` | It could not finish. This says nothing about the repo. |
Anything else is not a result. Each line above the last one is
`<state> <check> <detail>`, and the state is `ok`, `gap` or `unknown`.
`unknown` is never a pass: the script could not find out. Read the detail,
find out by hand, and report what you found.
| Check | It is `ok` when | Who fills a gap | Tier |
| --- | --- | --- | --- |
| `integration-branch` | `origin` has