メニュー
[QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
[Testing] Review test cases for quality, determinism, completeness, data validity, coverage gaps, duplication, live environment verification, and behavioral triangulation against docs + live + source. Delegates browser verification to qa-testing-expert; triangulation to ba-system-analyzer.
[Testing] Postman MCP collections — create, configure, verify, and export collections with proper variables, auth, and endpoints
[Testing] Autonomous test coverage gap analysis and generation — identifies missing test cases, generates enriched CSV test cases, validates P0 cases via browser, and reports improvements. Single-agent counterpart to /qa-coverage-generation.
Repo/tracker routing library for the vc-fix plugin — decides which external product repo owns a bug (client vs platform), whether the fix delivers as a direct PR, a fork-PR, or an upstream issue, and which VCS/tracker host to talk to. Used by /qa-fix and /project-init. Self-contained — no dependency on the ci/ directory.
Build, launch, smoke-test, and health-check the vc-mcp-testing-module agentic QA tooling repo. Use when asked to run, start, verify, smoke-test, or sanity-check this repo's tooling — env:check, @td() resolution, suite manifest sync, critical-UI-scope, seed dry-run, GraphQL fixture validation — or before running regression.
[QA Methodology] Triage a completed regression run's failures: collect each FAIL + its evidence (trace, screenshots, console, network) + failing CSV row, dedup + flag flaky, classify each into real-product-bug vs test-defect (bad steps / bad assertion / stale test data / stale test) vs flaky/env/known, live-verify the real ones, then route test-defects to /qa-review-tests --fix and draft bug reports. Detect-classify-verify-report only — never files a tracker ticket, never triggers /qa-fix.
| name | qa-evidence |
| description | [QA Method] Evidence capture & report formatting: screenshot rules, 3-tier verbosity, output paths. |
| argument-hint | [compact|detailed|signoff] |
| disable-model-invocation | true |
Apply the project's evidence capture policy and output path conventions. Use before any test execution session to ensure consistent artifact collection.
/qa-evidence # Full policy review (capture rules + output paths)
/qa-evidence compact # Compact reporting tier rules
/qa-evidence detailed # Detailed reporting tier rules
/qa-evidence signoff # Sign-off reporting tier rules
tests/, bugs → reports/bugs/, regression → reports/regression/, raw browser output → test-results/)| When | What | Naming |
|---|---|---|
| Test FAILS | Failure state screenshot | {TC-ID}-FAIL-{description}.png |
| Bug found | Bug evidence (annotated) | BUG-{name}-evidence.png |
| Visual regression | Before/after comparison | {component}-{state}-{viewport}.png |
| Critical flow final state | Confirmation/success page | {flow}-final-state.png |
| Error state | Console panel, network 500, error toast | {TC-ID}-error-{type}.png |
| Tier | Use When | Content |
|---|---|---|
| Compact | Regression suite pass, smoke run | Pass/fail table + bug list only |
| Detailed | Sprint testing, tracker ticket testing | Full test case results + evidence |
| Sign-Off | Pre-release, stakeholder review | Detailed + summary + risk assessment |
| Artifact | Directory |
|---|---|
| Test docs (plans, cases, reports) | reports/tickets/SprintXX-XX/VCST-XXXX/ |
| Screenshots (test evidence) | reports/tickets/SprintXX-XX/VCST-XXXX/screenshots/ |
| Bug reports | reports/bugs/ |
| Bug evidence | reports/bugs/screenshots/, reports/bugs/api-traces/ |
| Regression reports | reports/regression/ |
| Raw browser artifacts (gitignored) | test-results/{browser}/ |
test-results/ (gitignored)tests/ or reports/ (tracked)