Setup

Configure this repository for the Skrrt ship workflows and select a branching strategy. Run once before commit, pr, and release.From its SKILL.md

Install

npx -y skills add skrrt-sh/skills --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, as published. Nobody here has run it

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 create CLAUDE.md or AGENTS.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.md already exists, report its configured strategy before replacing it. Only the skrrt:policy block 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.

What ships with it: 2 files

7.4 KB alongside SKILL.md

evals/

trigger-evals.json2.0 KB

reference/

branching-strategies.md5.4 KB

Gives 0 of the 12 instructions most project setup skills give

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Select the first existing instruction file
Read references/branching-strategies.md
Inspect the repository signals it names
Present branching strategies with a recommendation
Report the configured strategy if agents ship md exists
Run the configure ship script

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.