mini auto

Chains phases on its own (next → plan → do → done), pausing for human checks.

↔ See the interactive form (/mini:…)

Usage

mini auto [options]

  --max-turns <n>  Cap each Claude session at N responses (saves tokens)
  --bump <level>   Version bump on each phase close: none | patch | minor | major (default none); required with --push
  --push           Push each phase commit to the remote (requires --bump patch|minor|major)

Description

The terminal command. Runs the whole phase loop on its own — next → plan → (do → done) for each step — driving the phase without you steering each one. It is not fully unattended: it stops and asks a human at items for manual verification (verify). --max-turns caps each Claude session; --bump and --push apply the version switches when closing each phase (--push requires an explicit bump).

At your own risk. To let the loop run with fewer interruptions, people sometimes start Claude Code with --allow-dangerously-skip-permissions (or leave it in acceptEdits) so it stops asking before each action. That hands Claude a free hand over your files and shell. mini only orchestrates the phases — it does not review or guarantee what Claude does, so any mistakes are yours to catch. Run it on a clean git working tree, keep the changes reviewable, and do not point it at anything you cannot afford to have changed.

Examples

# Drive the current phase autonomously
mini auto

# Cap session length and push a patch release on close
mini auto --max-turns 40 --bump patch --push

→ How mini adapts to your project