shiplisted
Install: claude install-skill samiraklf/claudrunner
# Ship
The last step is where unattended runs go wrong. Follow it exactly.
## 1 — Clean
Run the configured format command on the changed files. Run the configured lint command and
fix what it reports. Check the diff for leftovers: debug prints, commented-out blocks,
temporary files, stray test fixtures.
## 2 — Respect the autonomy level
Read `autonomy` from `.claudrunner/config.yml`:
- `suggest` — push nothing. Write the report and stop.
- `pr-only` — push the working branch, open a pull request.
- `push` — push to the branch named in the config, and only that branch.
**Never push to the default branch at any level. Never merge. Never force-push.**
The three host-specific steps — push, propose the change, return its link — are defined by
`project.host`. Read that host's `HOST.md` before proposing: on GitLab the change is a merge
request, and on Azure Repos it can carry its work-item link directly. Everything before the
push is plain git and identical everywhere.
## 3 — The pull request body
Five sections. No more.
**What** — one short paragraph per item, linking the item.
**Why** — the problem each change solves, from the item's perspective. Not a restatement
of the diff; the reviewer can read the diff.
**Tests** — which tests ran and what they returned. Real outcomes. Never ask the reviewer
to run them for you.
**Reviews** — one line per reviewer: findings count, and what was fixed.
**Known minor findings** — the P2 list, if any.
Add nothing else. No attribution