Reference

CLI Commands

Testonaut is driven by the testonaut CLI, locally or from an Azure pipeline. The commands map directly onto the four agent phases plus governance.

Scaffolding and readiness

# Scaffold the .agents config into a target repository
testonaut init --repo ./my-app

# Recreate generated files intentionally
testonaut init --repo ./my-app --force

# Check whether the repository is configured for Testonaut
testonaut check --repo ./my-app

init scaffolds AGENTS.md, .agents/testonaut.config.json, .agents/test-architecture.md, and .agents/test-conventions.json. It refuses to overwrite existing Testonaut files by default. check emits a ReadinessReport.

design-tests (Phases 1 + 2)

# Research the ticket and design tests, upload to Xray
testonaut design-tests --issue FINT-1056 --repo ./my-app

# Add the bounded LLM retrieval loop for large tickets
testonaut design-tests --issue FINT-1056 --repo ./my-app --deep

# Preview the Xray upload without mutations
testonaut design-tests --issue FINT-1056 --repo ./my-app --dry-run
FlagPurpose
--issue <KEY>Jira story to research and design for.
--repo <path>Local repository for Gherkin step reuse and skill overrides.
--deepEnables the bounded LLM retrieval loop before design.
--gateAC coverage enforcement: required, warn, or off.
--derive-requirementsEnables implied requirement mining.
--adversarial-critiqueEnables the design critique pass.
--risk-coverageRisk/edge gate: required, warn, or off.
--test-fieldsExtra Jira fields for created Xray Test issues.
--reporterSets Reporter on created Test issues.
--dry-runPreview Xray upload without mutations.
--yesConfirms upload when human review is required.

implement-tests (Phase 3)

# Implement from the story's linked Xray tests and raise a PR
testonaut implement-tests --issue FINT-1056 --repo ./my-app --pr

# Implement from a local design artifact
testonaut implement-tests --design out/FINT-1056/test-design.json --repo ./my-app
FlagPurpose
--issue <KEY>Reconstruct implementation input from Xray.
--design <path>Use a local TestDesignPack.
--stack <id>Selects a configured stack (default: first stack).
--no-envDisable the Docker/environment-aware flow.
--no-verifySkip verification.
--verify <command>Override the stack verify command.
--max-heal-attemptsHealing retry budget (default 1).
--prCommit, push, and raise a pull request.

respond-to-pr (Phase 4)

testonaut respond-to-pr --repo ./my-app --pr 42 --issue FINT-1056

# Classify and report only — no edits, no comments
testonaut respond-to-pr --repo ./my-app --pr 42 --issue FINT-1056 --dry-run
FlagPurpose
--pr <id>Pull request id to inspect.
--mention <handle>Override the PR mention handle (default @testonaut).
--max-iterations <n>Override the PR-wide response budget.
--verify <command>Override the stack verify command for this run.
--dry-runReport without editing files or posting comments.
--config <path>Load runtime configuration overrides.

audit

testonaut audit
testonaut audit --target FINT-1056
testonaut audit --action pr.raised --limit 20
testonaut audit --json

Unattended runs

The same commands run inside the parameterized Azure pipeline; Jira Automation passes mode, issueKey, and targetRepo — see the Jira Integration guide for the pipeline parameters and rule setup.