jmb-setup
jmb-setup
Leave in the project what the kit's skills expect from it, or bring it up to date. Everything goes into files of the repo, so that the flow works the same on another machine, in the cloud or for another person. It is a guided skill, not a script: it explores, shows what it finds, asks what is missing and writes when the human confirms.
| Piece | Where | Comes from |
|---|---|---|
| The project's data | docs/agents/flow.md |
templates/flow.md |
| The flow, the "Languages" table and the "Agent skills" section | AGENTS.md, between the jmb-setup markers |
templates/agents-md-block.md |
| The cross-cutting criteria | AGENTS.md, right before the markers |
templates/cross-cutting-criteria.md |
| How to use the tracker, where the spec goes and the "Wayfinding operations" section | docs/agents/issue-tracker.md, between the jmb-setup markers |
templates/issue-tracker.md |
| The triage labels | docs/agents/triage-labels.md, between the jmb-setup markers |
templates/triage-labels.md |
| Where the glossary and the ADRs live | docs/agents/domain.md, between the jmb-setup markers |
templates/domain.md |
The git hook and attribution |
.claude/settings.json |
templates/settings.json |
.claude/worktrees/, only with § Worktree |
.gitignore |
One line |
| Squash only, and the branch deleted on merge | The repo's settings on GitHub | Step 5 |
The hook, block-dangerous-git.sh, lives in this folder, and settings.json hooks it here: npx skills update brings it up to date along with the skills. Everything else is brought up to date by rerunning this skill.
It is idempotent: rerun on a project that has not changed, it changes nothing. What is already written is not asked again, and a file is written only if its content changes. In the project's files it rewrites what belongs to this skill: what is between its markers, keeping the project's values (those of the "Languages" table and the rows the project has added to it, the "Label in our tracker" column and "PRs as a request surface"), and its entries in settings.json. Outside that, only what the human confirms changes. Rerunning it is also the way to add a section of the contract that is missing, such as § Worktree, which turns on parallel mode.