qa

Run tests, lint, and operational-context checks to produce qa-report.md.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/jackson2787/torque-coding --skill qa-jackson2787
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/jackson2787/torque-coding/tree/main/skills/state-machine/qa
Command: npx skills add https://github.com/jackson2787/torque-coding --skill qa-jackson2787

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA verifies that a build is truly complete by running tests, linting, and checks, producing a verifiable qa-report.md and preventing premature "done" claims.

Core Features & Use Cases

  • Post-build verification: runs tests, linting, and operational-context checks to confirm acceptance criteria.
  • Evidence on disk: requires and validates artifacts on disk (qa-report.md, plan_context etc).
  • Audit trail: surfaces issues to BUILD when checks fail and guides escalation.

Quick Start

After BUILD declares completion, run the QA cycle to generate a qa-report.md and surface any failing checks.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a build is truly complete before declaring done?▼

Post-build verification confirms a build is complete by running tests, lint, and operational-context checks to generate a qa-report.md that proves acceptance criteria were met.

What is on-disk evidence for build validation and why do I need it?▼

On-disk evidence for build validation requires verifying artifacts like qa-report.md and plan_context physically exist on disk to avoid false positives and prevent premature done claims.

How do I generate an audit trail when build checks fail?▼

To generate an audit trail when checks fail, the QA process surfaces actionable issues to BUILD and guides escalation by validating strict disk artifacts instead of relying on runtime states.

Can I run lint and test verification without a plan_context file?▼

No, test and lint verification operates strictly on disk artifacts and plan_context to avoid false positives, requiring these files to validate acceptance criteria and produce a qa-report.md.

What happens when linter or test failures occur during post-build verification?▼

When linter or test failures occur during post-build verification, the process surfaces actionable issues to BUILD and guides escalation rather than allowing a premature completion claim.