spw.quest
Initialize the workbench in this repository.
Choose who runs the setup. Copy one block. Run it from the repository root. It stops before any commit.
Spw Workbench adds the Spw language, parser, CLI, and editor tooling. It mounts at .spw/_workbench; your repository keeps its own .spw/. It needs Git and Node 20.19+ or 22.12+.
test -d .git || git init git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench git -C .spw/_workbench checkout 3eaab637767222ffe248449da7262a251c4c608b npm --prefix .spw/_workbench ci --ignore-scripts npm --prefix .spw/_workbench run spw:init -- ../.. npm --prefix .spw/_workbench run spw:doctor -- ../.. git diff --check
This copy now ends with the five git commands. They do not commit.
claude -p 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'
This copy now ends with the five git commands. They do not commit.
codex exec 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'
This copy now ends with the five git commands. They do not commit.
grok 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.'
This copy now ends with the five git commands. They do not commit.
Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.
Git is already in the commands above. The same five commands are at git.txt and git.md.
Git, in this order
Use this when the block you copied does not already run git. Run only the command that matches the folder you have.
- No
.gityet →git init. Creates the repository. - No
.spw/_workbenchin.gitmodules→git submodule add. Records where the workbench comes from. - Link just added →
checkout. Pins the reviewed revision. - Link recorded, folder empty →
submodule update --init. Downloads that revision. git diff --checkonly looks. It does not edit or commit.
test -d .git || git init git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench git -C .spw/_workbench checkout 3eaab637767222ffe248449da7262a251c4c608b git submodule update --init -- .spw/_workbench git diff --check
When it worked
Same result for every choice above.
spw:doctorfinishes with no errors.- These files exist:
.spw/README.md,.spw/index.spw,.spw/mount.spw,.spw/workspace.spw,.agents/workflows/commit-review.md. The initializer may add a few more. - Nothing was committed. Read the diff, then commit it yourself.
Then, if you want
After doctor, give the same agent one question about this repository. Skip this if you only wanted the mount.
Read .spw/README.md, .spw/index.spw, .spw/workspace.spw, and .spw/mount.spw. Treat .spw/_workbench as mounted infrastructure. The consumer owns the surrounding .spw tree. Choose one bounded question about this repository. Navigate before reviewing: npm --prefix .spw/_workbench run spw -- roots npm --prefix .spw/_workbench run spw -- tree @spw --depth 3 Use the mounted-consumer review skill only as an instrument, following this repo's rules. Record evidence under consumer-owned .spw/audits/ with consumer and workbench revisions. Keep this repository's own CSS nouns, copy, and framework.
Full recipe · Prompts · quest.json · Upstream quick start · What was hard to follow