fixlisted
Install: claude install-skill pdemagny/logistics
# /fix: from a bug report to a PR
The user's request: `$ARGUMENTS`
This skill runs Spec Kit's bug extension (assess, fix, test) in subagents,
then a code review and the ship, stopping at gates where the user decides.
Nothing gets merged, and nothing is called fixed until an agent that did not
write the fix has verified it.
Read `<this skill's base dir>/../feat/references/harness.md` now: it holds
the rules this skill follows. The values it refers to are below. If it is
missing, stop: "/fix needs logistics' `feat` skill
(references/harness.md); install or update logistics".
## Harness values
- *Skill*: `fix`.
- *Artifact dir*: the bug dir, `.specify/bugs/<slug>/`.
- *State file*: `.specify/bugs/<slug>/feat-state.md`, created at setup
step 7.
- *The state file is created*: when setup step 7 creates it.
- *Title* and *input section*: `# /fix state: <bug title>`; `## Report`,
the argument as given.
- *Size line*: `not set | small | medium | large`.
- *Agents line*: `none (every spawn is fresh)`.
- *Current phase values*: `<N> <name>` (0–5), `done (shipping)`,
`done (PR #N)` (local copy only), `done (not a bug)`, `done (invalid)`.
- *Map line*: `none`.
- *Issue ref*: the `Issue:` line of the state file (`none`: no issue, so
no board moves and no `Fixes` line). It is the report's issue, or the one
created after the assess gate (phase 1, "Issue creation").
- *Done marker*: `Current phase:` starts with `done`, except a `done
(shipping)` run whose branch has no upstre