codeclawlisted

<!-- codeclaw-begin --> # codeclaw Skill ## THE RULE **Every `codeclaw` command outputs `next_steps`. FOLLOW THEM.** Do not memorize the flow. Do not skip steps. Do not improvise. Run the command -> read the output -> follow `next_steps`. That's it. The CLI tracks your stage (1-4: auth -> configure -> review -> done). `codeclaw export` (push) is **gated** -- you must run `codeclaw confirm` first or it will refuse. ## Getting Started Run `codeclaw status` (or `codeclaw prep` for full details) and follow the `next_steps`. ## Output Format - `codeclaw prep`, `codeclaw config`, `codeclaw status`, and `codeclaw confirm` output pure JSON - `codeclaw export` outputs human-readable text followed by `---CODECLAW_JSON---` and a JSON block - Always parse the JSON and act on `next_steps` Key fields: - `stage` / `stage_number` / `total_stages` -- where you are - `next_steps` -- follow these in order - `next_command` -- the single most important command to run next (null if user input needed first) ## PII Audit (Stage 3) After `codeclaw export --no-push`, follow the `next_steps` in the JSON output. The flow is: 1. **Ask the user their full name** -- then grep the export for it 2. **Run the pii_commands** from the JSON output and review results with the user 3. **Ask the user what else to look for** -- company names, client names, private URLs, other people's names, custom domains 4. **Deep manual scan** -- sample ~20 sessions (beginning, middle, end) and look for anything sens