aiox-apply-qa-fixes

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

3.1k|952|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/SynkraAI/aios-core --skill aiox-apply-qa-fixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-apply-qa-fixes
Source: https://github.com/SynkraAI/aios-core/tree/main/.grok/skills/aiox-apply-qa-fixes
Command: npx skills add https://github.com/SynkraAI/aios-core --skill aiox-apply-qa-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a QA review gate returns FAIL or CONCERNS on a story, developers need a disciplined way to remediate every finding without losing track of items or prematurely marking work as done. This Skill operationalizes that remediation loop inside the AIOX framework.

Core Features & Use Cases

  • Complete findings inventory: Enumerates all QA gate findings before fixing, then resolves each as FIXED, WON'T_FIX (justified), or DEFERRED (with owner), prioritizing CRITICAL/HIGH over MEDIUM/LOW.
  • Verification gates: Re-runs lint, typecheck, and tests after fixes, and updates the story's File List and QA Results resolution notes.
  • No self-approval: Explicitly forbids self-approving the gate, setting Status to Done, or pushing to git; always hands back to the review-story workflow.
  • Use Case: After a QA review flags a story with gate FAIL, invoke this Skill with the story path to systematically remediate findings and return the story for re-review.

Quick Start

Ask the agent to apply QA fixes to your story file, for example by providing the story path and choosing yolo or interactive mode.

Frequently Asked Questions about aiox-apply-qa-fixes

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

FAQPage Schema
How do I apply QA fixes after a failed quality gate review?

Invoke the skill with the story path as the first argument and an optional 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 inputs does the apply QA fixes workflow require?

It requires a story path containing QA Results or a gate file as the first argument, plus an optional mode argument. The story must already have been through a QA review so findings exist to remediate.

Can this workflow mark a story as Done after fixing findings?

No. The skill explicitly forbids setting Status to Done, self-approving the gate, or running git push. After fixes, the story is handed back to the review-story workflow for an independent re-review.

How are QA findings prioritized and resolved during remediation?

All findings are inventoried first, then CRITICAL and HIGH severity items are fixed before MEDIUM and LOW. Each finding is resolved as FIXED, WON'T_FIX with justification, or DEFERRED with an assigned owner.

What verification happens after QA fixes are applied?

The workflow re-runs npm run lint, npm run typecheck, and npm test, then updates the story's File List and QA Results resolution notes. A post-phase checklist confirms findings are addressed and the story is still not Done.