Configure Ship Workflows
Create a short agent-instruction pointer and a detailed .agents/ship.md policy for this
repository.
Process
Confirm the current directory is a Git repository.
Select the first existing instruction file from
CLAUDE.md,AGENTS.md,.claude/CLAUDE.md, and.github/AGENTS.md. If none exists, ask the user whether to createCLAUDE.mdorAGENTS.md.Read references/branching-strategies.md. Inspect the repository signals it names, then present GitHub Flow, Trunk-Based Development, and Gitflow with one evidence-based recommendation. The user makes the final choice. If they already named a strategy, treat that as their choice after reporting any material mismatch.
If
.agents/ship.mdalready exists, report its configured strategy before replacing it. Only theskrrt:policyblock is replaced; anything the repository added outside it is kept.From the target repository, run:
${CLAUDE_SKILL_DIR}/scripts/configure-ship.sh \ --instruction-file <path> \ --strategy <github-flow|trunk-based|gitflow>Report the instruction file, selected strategy, and whether each file changed.
The script may modify only the selected instruction file and .agents/ship.md. It preserves
content outside Skrrt markers, removes the legacy skrrt:branching block during migration, and is
safe to run repeatedly.