/mini:auto

Slash command that runs the autonomous phase loop from inside Claude Code.

↔ See the non-interactive form (mini …)

Usage

/mini:auto [--max-phases N] [--yolo] [--verify] [--discuss] [--bump <level>] [--push]

  --max-phases N  How many phases to complete in a row (default 1)
  --yolo          Fully unattended (needs the session in acceptEdits)
  --verify        Force the human verify step in every phase
  --discuss       Force the discuss step in every phase
  --bump <level>  Version bump on each phase close: patch | minor | major
  --push          Push each phase to the remote (requires --bump)

Description

The native slash command, run inside your Claude Code session. It runs the phase loop autonomously — next → discuss(conditionally) → plan → do → verify(conditionally) → done — completing whole phases in a row up to --max-phases. It still stops and asks you at the next proposal and at human verify; --yolo runs unattended (only with the session in acceptEdits), --verify/--discuss force those steps in every phase, and --bump/--push apply the version switches when closing each phase. This is the in-session counterpart of the `mini auto` terminal command.

At your own risk. --yolo only works with the session in acceptEdits, and some people go further and start Claude Code with --allow-dangerously-skip-permissions so it never pauses to ask. That removes the safety prompts entirely and lets Claude touch any file or run any command on its own. mini drives the phase loop but does not vet what Claude actually does — it cannot guarantee the result is correct or safe, so the responsibility for catching mistakes is yours. Use it only on a clean git working tree you can review and roll back.

Examples

# Complete one phase autonomously
/mini:auto

# Three phases in a row, patch-bumped and pushed on each close
/mini:auto --max-phases 3 --bump patch --push

→ How mini adapts to your project