setuplisted

Adds skrrt skills instructions to the current project's CLAUDE.md or AGENTS.md so that commits, PRs, and releases use the ship plugin skills. Use this skill whenever the user wants to set up, configure, install, or wire skrrt skills into a project, add ship plugin instructions to agent config files, or ensure the team uses /commit /pr /release instead of raw git commands. Trigger even when the user says "set up this repo", "add skills to CLAUDE.md", or "configure the ship plugin".
skrrt-sh/skills · ★ 2 · Data & Documents · score 78

Install: claude install-skill skrrt-sh/skills

# Ship Setup Skill Append two marker-delimited blocks to the project's agent instruction file: the ship skills block and a branching strategy block. ## Workflow 1. **Find the instruction file** — first of `CLAUDE.md`, `AGENTS.md`, `.claude/CLAUDE.md`, `.github/AGENTS.md`. Create `CLAUDE.md` in the project root if none exists. 2. **Append the ship block** unless `` is already present. 3. **Recommend a branching strategy** unless `` is already present. Read [reference/branching-strategies.md](reference/branching-strategies.md), gather the signals it lists from the actual repo, then present all three options with one marked as recommended and your reasoning stated. The user chooses; append the matching block. If the marker already exists, read the heading after it to report the configured strategy and offer to replace it. Replacing means swapping everything between `` and `` inclusive. 4. **Report** which file changed and which blocks were added. Extra environment tiers beyond dev/staging/production need no block edit — they are just more `vX.Y.Z-<env>.N` tags, and CI parses the suffix to pick the target. ## Blocks Append these verbatim, markers included. ```markdown  ## Git workflow — skrrt skills Use `/commit` for commits, `/pr` for pull and merge requests, and `/release` for releases — prefixed `/ship:` when installed as a Claude Code pl