apply-qa-fixes

Applies QA gate findings to a story and hands it back for re-review.

1|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill apply-qa-fixes-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apply-qa-fixes
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.claude/skills/apply-qa-fixes
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill apply-qa-fixes-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a QA review gate returns FAIL or CONCERNS on a story, someone must systematically remediate every finding without cutting corners or prematurely marking the work done. This Skill enforces a disciplined fix workflow that addresses all findings and returns the story for re-review instead of self-approving. ## Core Features & Use Cases - Complete findings inventory: Catalogs every QA finding before fixing, then resolves CRITICAL/HIGH items before MEDIUM/LOW, with each finding marked FIXED, WON'T_FIX (justified), or DEFERRED (with owner). - Gate re-verification: Re-runs lint, typecheck, and test commands after fixes and records resolution notes in the story's File List and QA Results sections. - No self-approval guardrails: Explicitly forbids setting the story to Done, self-approving the gate, or pushing to git, and hands the story back to the review-story workflow. - Use Case: After a QA gate marks a story FAIL with three HIGH findings, invoke this Skill with the story path to remediate each finding, re-run the checks, and route the story back for an independent re-review. ## Quick Start Ask the agent to apply QA fixes to the story file at the given path in interactive mode so every gate finding is remediated and handed back for re-review.

Frequently Asked Questions about apply-qa-fixes

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

FAQPage Schema
How do I fix QA gate findings on a story?▼

Invoke the Skill with the story path and a mode (yolo or interactive). It inventories all findings, fixes CRITICAL and HIGH items first, re-runs lint, typecheck, and tests, then hands the story back for re-review.

What happens to findings that cannot be fixed?▼

Each finding is marked FIXED, WON'T_FIX with a justification, or DEFERRED with an assigned owner. Nothing is silently dropped; the complete findings inventory is recorded in the story's QA Results resolution notes.

Can this Skill mark a story as Done after fixes?▼

No. The Skill explicitly forbids setting Status to Done, self-approving the gate, or running git push. It always hands the story back to the review-story workflow for independent re-review.

What inputs does the apply-qa-fixes workflow require?▼

It requires a story path containing QA Results or a gate file, plus an optional mode argument (yolo or interactive). The detailed task definition lives in .aiox-core/development/tasks/apply-qa-fixes.md, which acts as the source of truth.

Which checks are re-run after applying QA fixes?▼

The protocol re-runs npm run lint, npm run typecheck, and npm test after fixes are applied. Results are noted in the story so the re-review can verify the gate criteria are actually met.