Strip AI tells from a markdown file (Korean or English) while preserving meaning. Single-pass workflow: scan with bin/divecode-humanize-scan, apply targeted rewrites per checklists/humanize-{ko,en}.md taxonomy, re-scan to verify, output a before/after report. Hard guard: change rate > 30% warns, > 50% halts. Use when asked to "humanize this", "AI 티 없애줘", "drop the AI tone", "윤문해줘", or to post-process drafted text before publishing. Korean taxonomy is a focused subset of im-not-ai (https://github.com/epoko77-ai/im-not-ai). English taxonomy is divecode's own collection. Use im-not-ai directly for deeper Korean analysis with academic-cited patterns.
PRD interrogation entry point — the product wedge of divecoding. Takes a rough PRD (path or pasted text), fires pattern-pack triggers, surfaces per-pack failure modes as a risk-map, and drives an interrogation loop that asks the 8-12 questions the PRD didn't answer. Produces design.md (Spec §2 populated from PRD), risk-map.md, and open-questions.md before any code is generated. Use when starting a new bolt with a written PRD. For cold-start (no PRD), fall through to /divecode-spec instead.
The always-on Genie pause for ad-hoc commands. Lighter than /divecode-prd — no PRD file required. Takes any user request ("build me a thing", "fix this bug", "add caching here") and runs three Genie questions before any code is generated: 1. What you literally asked for is X — confirm. 2. Things you didn't specify but X depends on: A, B, C. 3. Specify those now, or grant X literally and accept the consequences? Pattern packs supply A, B, C — same trigger matcher as /divecode-prd, just fed the user's ad-hoc request instead of a PRD file. Use when the user drops a one-line or paragraph-long command and you're tempted to just execute it. Voice triggers: "wish", "genie", "before you build", "are you sure".
Inception sub-phase for in-progress projects. Reads existing source + .md docs + sibling repos + relevant OSS ecosystem to surface SILENT DECISIONS (those made by action or omission without recorded rationale). Produces divecode/audit-<feature>.md. Auto-invoked from /divecode entry when in-progress detected (feature/* branch or existing source on main). Use when starting divecode on an existing project, or asked to "audit this feature", "what decisions are silent", "review the in-flight work".
Final phase of the bolt. Delete the working branch + worktree (if any), sync the integration branch, archive the bolt's marker so subsequent runs do not resume it, and prompt the user to write a lore entry if the bolt produced architectural decisions worth preserving. Use after /divecode-merge.
Group bolt changes into logical commits per profile.commit_convention. Honors style (conventional | freeform) and co_author (include | omit). Use after /divecode-fix-loop (or /divecode-review if no must-fix), before /divecode-push-pr.
Address review findings from final-review.md. Max 3 rounds; escalates to user if must-fix items remain after round 3. Tests stay green after each round. Use after /divecode-review when must-fix findings exist; before /divecode-commit.
Implementation phase of divecode. Reads requirements, design, and ARCHITECTURE, then writes code in small slices — each slice paused for human review. Iron Law: no slice exceeds what a human can sanely review in one sitting (~150 lines or one logical unit). Surfaces drift from the spec ("the architecture said X but doing it strictly creates Y problem — should we revise the architecture or accept the trade-off?"). Use after /divecode-arch.