init

Topics in the source

• init
• When to load
• First install — ask for the profile
• Setup interview
• After a first install — questions init prints
• Other invocations
• Gotchas

Bootstraps the claude-arsenal/ framework in the host repository. Run once per repo; re-run to add workspaces or refresh the bundle. The script prints what it created, refreshed and skipped, so relay its output rather than re-describing it. The parts below are the ones that need the user. CANARY: init-loaded-2026-06-13-fb78d23e-a1b2c3d4e5f6a7b8 A repo needs the task queue set up for the first time ("init the arsenal", "/init"). Adding a new workspace to an existing claude-arsenal/ setup. Every installed skill adds a row to the skills listing of every future session in this repo, so ask before installing, when arsenal/config.toml has no [skills] table yet: What kind of project is this? python (adds the Python toolchain skills), general (spec/design/execute/review/ship), or minimal (queue and GitHub only)? Take the answer from the user rather than the file tree: a repo with .py files is not necessarily one whose release process this bundle should advise on. The profile is written as an editable [skills] table; --sections workflow,python names sections directly instead. On a first install, whenever init prints SETUP INTERVIEW PENDING (no setup-interview in arsenal/config.toml, on any r

This is an excerpt. Refer to the complete source and its current requirements.