CLI

Execution Workflow

1. Install the CLI extra when standalone alchemy commands are needed.
2. Point every command at an explicit dotted config path via --config.
3. Use init, make-migrations, upgrade, and downgrade as the core lifecycle.
4. Use inspection commands such as check, heads, history, and show-current-revision in CI or troubleshooting.
5. Use branch-management and utility commands only when the migration graph actually requires them.

Implementation Rules

• Prefer explicit config paths over implicit discovery in automation.
• Keep destructive commands such as drop-all behind clear environment guards.
• Use check in CI for drift detection before deployments.
• Embed the CLI into Click or Typer only when the project already has an application CLI worth extending.

Example Pattern