← ClaudeAtlas

initlisted

Use when setting up DevFlow in a repo for the first time, or after a plugin update — scaffolds .devflow/config.json from the shipped template (when absent) or backfills newly-added keys into an existing one (preserving your values), and refreshes config.schema.json. Invoke explicitly with /devflow:init.
The01Geek/devflow-autopilot · ★ 3 · Code & Development · score 72
Install: claude install-skill The01Geek/devflow-autopilot
# DevFlow Init Scaffold this repo's DevFlow config files. **One command does everything — do not hand-write `config.json` or guess field values.** **Consumer prompt extension (load first).** Before doing this skill's work, load any consumer-supplied prompt extension for this skill and honor it. From the repo root, run: ```bash ${CLAUDE_SKILL_DIR}/../../scripts/load-prompt-extension.sh init ``` If the helper exits non-zero, a consumer extension exists but could not be loaded — surface its stderr message and do not silently proceed as if none existed. If it exits 0 and prints text, treat that text as additional instructions appended to the end of this skill's own prompt for this run — it is upgrade-safe, consumer-owned customization committed under `.devflow/prompt-extensions/`. If it exits 0 and prints nothing, proceed unchanged. ## Run ```bash bash "${CLAUDE_SKILL_DIR}/../../scripts/scaffold-config.sh" ``` This is the single shared scaffolder — the same script `install.sh` uses, so the two entry points can never drift. With no argument it targets the current repo root (git toplevel) and: - creates `.devflow/config.json` from the shipped `config.example.json` **only if it does not already exist** — it never clobbers a config you've already filled in. When the config already exists it's kept and re-running **backfills any newly-added keys** from the example (at any nesting depth) so you can opt into new features; values you've already set always win and arrays you've tu