afk-setuplisted
Install: claude install-skill Warshoow/afk.sh
# /afk-setup
`afk.sh` is bare. Its defaults are cut for a pnpm monorepo; everything else (Python,
PHP, Rust, flat npm, monorepo in two halves) has to declare its own gate.
This skill reads the repo and writes `.afk.env` at its root.
**Only one question matters: which command says "this ticket is done" here?**
Everything else has a correct default. Only write into `.afk.env` what differs.
## 1 — Prerequisites
```bash
test -f docs/agents/issue-tracker.md && grep -qi github docs/agents/issue-tracker.md
```
Missing or non-GitHub → **stop**. Tell the user to run
`/mattpocock-skills:setup-matt-pocock-skills` first: `afk.sh` refuses to start without
it, and triage will not have its labels.
Also flag (without blocking) the absence of `CONTEXT.md` / `CONTEXT-MAP.md` / `docs/adr/`:
the sessions will run with no project memory.
## 2 — Find the gate
Read, in this order — the lower sources are authoritative over the ones above:
1. `package.json` (scripts), `pyproject.toml`, `Cargo.toml`, `composer.json`, `Makefile`
2. **`.github/workflows/*.yml`** — what CI requires is the best available definition of
"done": it is the gate the PR will have to pass anyway
3. **`CLAUDE.md`** — often a hand-written "Commands" section, with the traps. The most
reliable of the three.
Aim for **fast and with no external service**. A 15-minute gate killed by `TIMEOUT`, or
one demanding a live Postgres, protects nothing: it fails healthy tickets.
## 3 — The traps that cost a run
| Trap | Sympt