Menu
[QA Method] Quality metrics & gates: pass rate, defect density, DRE, coverage tracking, quality gate enforcement.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Initialize / onboard this agentic-QA plugin onto a deployment. Installs deps, then asks the operator only what genuinely shapes the config โ the environment NAME, the bug tracker (Jira / Azure Boards), the code host (GitHub / Azure Repos), and an auth preference per axis (PAT recommended, else browser/CLI login). Everything else โ whether it is a native-platform or a CLIENT project, the client org, the contribution mode, the fork account โ is DERIVED from the token + the filled env + a live module/repo scan. Writes project-profile.json + .env.<env> + .env.local + .mcp.json and verifies access. The whole point is to make /qa-fix route each bug to the RIGHT repo (client custom code vs native platform) and file to the RIGHT tracker. Use when standing the plugin up on a new machine or for a new customer.
Initialize / onboard this agentic-QA plugin onto a deployment. Installs deps, then asks the operator only what genuinely shapes the config โ the environment NAME, the bug tracker (Jira / Azure Boards), the code host (GitHub / Azure Repos), and an auth preference per axis (PAT recommended, else browser/CLI login). Everything else โ whether it is a native-platform or a CLIENT project, the client org, the contribution mode, the fork account โ is DERIVED from the token + the filled env + a live module/repo scan. Writes project-profile.json + .env.<env> + .env.local + .mcp.json and verifies access. The whole point is to make /qa-fix route each bug to the RIGHT repo (client custom code vs native platform) and file to the RIGHT tracker. Use when standing the plugin up on a new machine or for a new customer.
[QA Methodology] Gather ALL fresh CI prerelease artifacts for a change (modules + platform + vc-frontend) and deploy them together to the test env (vc-deploy-dev@<TEST_ENV branch>) in ONE manifest update: resolve a tracker ticket's linked PRs across all repos (or an explicit --module/--platform/--theme/--pr set) โ each PR's latest vc3prerelease build โ minimal-diff repin of backend/packages.json (AzureBlob/BlobName + PlatformVersion) and theme/artifact.json โ dry-run combined diff (default) or a gated deploy PR (direct same-repo when the account has write, else a fork PR) โ --verify polls the env-branch pin + /api/platform/modules per target. Never merges (a human merges to deploy); writes route through gh's keyring token; prints the web-edit URL when it can't push. Unblocks /qa-test PR#N and /qa-verify-fix.
[QA Method] Triangulate each BL invariant against docs + live + source code, auto-apply confirmed changes to business-logic.md, and reconcile test-case coverage. Delegates the live axis to qa-testing-expert; runs the triangulation via ba-system-analyzer.
Bring up a local Virto Commerce stack (backend + storefront + DB + ES) via start-local, pinned to the ACTUAL deployed package manifest (vc-deploy-dev @ vcptcore-demo); optionally augment it with the module/PR versions a JIRA task needs. Use when asked to spin up / run / provision a local VC environment, reproduce a deployed env locally, or stand up an env to test a specific ticket.
[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.
| name | qa-metrics |
| description | [QA Method] Quality metrics & gates: pass rate, defect density, DRE, coverage tracking, quality gate enforcement. |
| argument-hint | [metrics|gates|report|trends] |
| disable-model-invocation | true |
Measure test effectiveness and enforce quality gates for sprint releases, full releases, and regression runs. Use to assess current quality posture, track trends, or validate go/no-go decisions.
/qa-metrics # Full overview (all metrics + gates)
/qa-metrics metrics # Metric definitions and formulas
/qa-metrics gates # Quality gate thresholds only
/qa-metrics report # Generate quality report from latest run
/qa-metrics trends # Analyze trends from history.json
Compute the numbers deterministically โ don't do the arithmetic by hand.
npm run metrics:compute -- --history reports/regression/history.json [--gate smoke|sprint|release|hotfix] [--suite <id>] [--since <ISO>] [--p0-bugs N] [--p1-bugs N] [--json](scripts/regression/compute-metrics.ts) is the single source for every formula inquality-metrics-catalog.md(pass/fail/blocked/skip rate, velocity, defect density) and every trend (sprint-over-sprint delta, rolling average, consecutive drops, flakiness), plus the gate verdict perquality-gates.mdยง9 (PASS/FAIL or APPROVED / WITH CONDITIONS / BLOCKED). It exits non-zero on BLOCKED/FAIL so it can gate CI. Pass-rate criteria are computed from the run history; open-P0/P1 bug counts come from JIRA, so supply them via--p0-bugs/--p1-bugs(default 0). The skill's job is to run this, then write the narrative around the numbers โ never to recompute them.
Determine the context:
metrics โ Read quality-metrics-catalog.md, list all metric definitionsgates โ Read quality-gates.md, show gate thresholds for the relevant release typereport โ Read both files, compute metrics from latest regression results in reports/regression/trends โ Read quality-metrics-catalog.md "Using history.json" section, analyze reports/regression/history.jsonFor quality reports:
reports/regression/quality-gates.mdFor trend analysis:
reports/regression/history.json (90-day rolling window)For go/no-go decisions:
quality-gates.md/qa-risk to determine which metrics matter most for current scope/qa-evidence for output formatting of quality reports/qa-risk)