qa-task

Invoke the qa-task skill once the task document exists at docs/tasks/task.[id].[name], all implementation phases are checked complete, tests pass, and a pull request is open on the feature branch. The skill verifies prerequisites, runs tests, reviews the diff, and writes a gate decision.

Story QA validates acceptance criteria for end-user features, while technical task QA validates success criteria across functional, performance, and code quality dimensions. Task QA also requires documented migration paths for breaking changes and assesses system-wide NFRs like reliability and maintainability.

Yes, the skill halts if no pull request exists for the current branch because it posts the gate decision as a PR comment. It uses gh pr comment on GitHub and the REST API on Bitbucket, with posting treated as best-effort and non-blocking.

Re-review is skipped only when the prior gate is PASS with no issues, no source commits occurred since the gate, the task document has not been edited, and its status was not reopened. Any code or document change since the gate triggers a fresh review.

A FAIL or CONCERNS gate documents all HIGH and MEDIUM severity issues as bug report files and returns the task for fixes. The qa-fix loop then addresses findings, and the next review cycle runs a full refute pass over the entire branch diff.