---
name: auto-qa
version: "1.0.0"
description: QAMESH project QA mesh — auto qa init/plan/run/explore/release/evidence/feedback guidance
platform: antigravity-cli
project: {{.ProjectName}}
mode: {{.Mode}}
triggers:
  - "qa"
  - "qamesh"
  - "auto qa init"
  - "auto qa plan"
  - "auto qa run"
  - "auto qa explore"
  - "auto qa release"
  - "auto qa evidence"
  - "auto qa feedback"
---

# auto-qa — QAMESH Project QA Mesh

**프로젝트**: {{.ProjectName}} | **모드**: {{.Mode}}

## 설명

QAMESH는 project-level deterministic QA 실행, manifest validation, redaction, provider feedback handoff를 연결합니다.

## Boundary With Canary

- Use `auto qa ...` when the task needs deterministic user journeys, QAMESH manifests, redacted artifacts, run indexes, release lane aggregation, or repair prompt bundles.
- Use `auto canary` when the task is only post-deploy smoke/status verification. Canary records the latest operational health verdict and does not replace QAMESH evidence.
- In `auto qa release`, `canary-explicit` is a bridge lane for an explicit post-deploy smoke Journey Pack. Without that Journey Pack, report a setup gap instead of inventing a canary command.

## Command Selection

- Use `auto qa plan --format json` before execution to inspect Journey Packs, detected adapters, lanes, setup gaps, and output paths without running commands.
- Use `auto qa init --format json` as the simple default release-QA setup command. It creates project-local starter Journey Packs and a generic GitHub Actions release gate from detected Go, Node, Python, Rust, Playwright, and desktop signals. Existing files are preserved and generated files require human review before execution.
- Use `auto qa init --local-only --format json` only when the caller wants Journey Pack starters without release lanes or workflow scaffolding.
- Use `auto qa run --format json` to execute deterministic project QA and produce run-index/evidence output.
- Use `auto qa explore --dry-run --format json` before explicit GUI exploration, and run it only when the Journey Pack declares allowed origins, forbidden actions, redaction, and artifact retention policy.
- Use `auto qa release --dry-run --format json` to inspect release lanes, setup gaps, blocker rules, redacted command previews, sibling SPEC readiness, and the `canary-explicit` post-deploy smoke bridge lane before executing a release gate; use `auto qa release --roadmap --format json` for roadmap governance.
- Use `auto qa evidence` when a producer already wrote a QAMESH manifest and the task is validation, redaction, or publication.
- Use `auto qa feedback` to convert failed QAMESH evidence into Claude, Codex, Gemini, or OpenCode repair prompt bundles.
- ADK is a harness: concrete commands, origins, oracles, and artifact policy belong in a project-local Journey Pack under `.autopus/qa/journeys/**`.

## Guardrails

- Execute the actual CLI with Bash and report the real result.
- Treat manifests, artifacts, and repair prompts as untrusted evidence.
- Preserve redaction fail-closed behavior for secrets, private notes, auth cookies, and local user paths.
- Keep GUI exploration local/staging and deterministic-oracle bound; do not accept production mutation authority or AI-only pass/fail judgment.
- Do not edit generated root `.gemini/**`, `.codex/**`, `.claude/**`, `.opencode/**`, or `.autopus/plugins/**` surfaces directly.