Scenario
Task: Add a health-check endpoint, tests, and documentation while preserving existing APIs.
Why this example: it is small enough to reproduce, has a deterministic check, and produces an easy-to-review file and test summary.
Use a disposable repository to add a health-check endpoint and tests while preserving the existing API. The workflow makes the plan, checks, recovery boundaries, and result visible.
Illustrative fixture. The demo does not claim a completed production change.
Prepare the repository, preview the change, and keep the result reviewable.
Check the CLI and local environment.
DoctorCreate or migrate a disposable repository.
RepositoryAsk for the change without applying it.
PlanReview checks, evidence, and stop reasons.
ResultConnect a plain-language task to a local repository, configured checks, and evidence you can inspect before applying anything.
Follow the full path below and keep the output with the disposable repository's change record.
Task: Add a health-check endpoint, tests, and documentation while preserving existing APIs.
Why this example: it is small enough to reproduce, has a deterministic check, and produces an easy-to-review file and test summary.
Install the CLI and check the environment:
curl -fsSL https://raw.githubusercontent.com/floticinfo/minitok-server/rust-migration/scripts/install-rust.sh | bash
minitok doctorFor an existing disposable repository:
cd your-disposable-repository
git init
minitok migrateThe promotion helper creates a local Git repository and writes a plan; it does not call a model or apply a change. Pass the printed absolute path to minitok migrate.
# POSIX shell
output="$(minitok promote demo)"
printf '%s\n' "$output"
fixture="$(printf '%s\n' "$output" | sed -n 's/^Demo fixture created: //p')"
minitok migrate "$fixture"
# PowerShell
$output = minitok promote demo
$output
$fixture = (($output | Where-Object { $_ -match '^Demo fixture created: ' }) -replace '^Demo fixture created: ', '').Trim()
minitok migrate $fixtureA configured provider and entitlement are still required for the model-backed preview:
minitok run --dry-run "Add a health-check endpoint, tests, and documentation. Preserve existing APIs."
minitok status
minitok run list
minitok run show <run-id>The first local success is a passing verification gate and inspectable evidence record.
VERIFY_CMD.mjs or configured check is the project check.If the plan and safety boundaries look right, run the same task without --dry-run only after confirming your provider, entitlement, approval policy, backups, and repository checks.
minitok does not replace Anthropic, OpenAI, Google, or another model provider. Provider credentials and model usage costs are separate.
minitok promote demo is onboarding evidence only, not model output or deployment proof. Verified means the configured checks passed; it does not guarantee correctness, security, deployment, or production readiness.This walkthrough follows the CLI's documented command shape. See the documentation, AI-assisted repository change case study, source repository, and GitHub Releases. For data handling, see the privacy policy.