skills.rest
gabrielnsmnto
gabrielnsmntoCOMMUNITY
Explore all skills by this author →
GitHub

dev-apply-qa-fixes

Applies fixes for QA gate findings and re-validates code before re-review.

3|Updated Feb 7, 2026
Search Tags:#testing#code review#linting#validation#quality gate#story workflow#qa fixes
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill dev-apply-qa-fixes-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-apply-qa-fixes
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/qa/dev-apply-qa-fixes
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill dev-apply-qa-fixes-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a story receives QA feedback with blocking issues, developers need a systematic way to review findings, prioritize fixes, apply changes, and re-validate without losing track of what was addressed. ## Core Features & Use Cases - QA Gate Report Review: Loads the QA gate YAML file from docs/qa/gates/ and categorizes issues as BLOCKING, WARNING, or RECOMMENDATION. - Systematic Fix Workflow: Creates a fix plan per issue, applies code changes following existing patterns, and updates tests as needed. - Validation & Re-submission: Runs linting, tests, and type checking, then updates the story's Dev Agent Record so the story is ready for QA re-review. - Use Case: After a QA reviewer flags missing error handling and failing tests in a story's gate report, use this Skill to work through each blocking issue, verify the fixes, and hand the story back for re-review. ## Quick Start Ask the agent to apply the QA fixes from the gate report for the current story and re-run the test suite.

Frequently Asked Questions about dev-apply-qa-fixes

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

FAQPage Schema
How do I fix issues found in a QA gate report?▼

Load the QA gate YAML file, categorize issues as BLOCKING, WARNING, or RECOMMENDATION, then create a fix plan per issue. Apply changes following existing codebase patterns, update tests, and run linting and the full test suite to validate.

How do I prioritize QA findings before applying fixes?▼

Prioritize by severity: BLOCKING issues must be fixed before approval, WARNINGs affect the quality score, and RECOMMENDATIONs are optional improvements. Group related issues that can be fixed together and estimate effort for each fix.

Where does the QA gate file come from?▼

The gate file is loaded from docs/qa/gates/. You can provide the path directly, or the workflow checks the story file's qa_results section for a gate_file reference. If neither exists, you will be asked for the path.

What validation should run after applying QA fixes?▼

Run npm run lint, npm test, and npm run typecheck if applicable. Confirm all BLOCKING issues are resolved and regression tests still pass before marking the story ready for QA re-review.

Should I update the qa_results section after fixing issues?▼

No. Only update the story's Dev Agent Record section with completion notes and the file list. The qa_results section is reserved for the QA reviewer and must not be modified by the developer.

Related Skills

Explore More Software Engineering Skills→
SynkraAISynkraAI
3.1k

aiox-review-story

Reviews a development story and writes a QA gate verdict with lifecycle status transitions.

Official
Intermediate
gaiastudio-aigaiastudio-ai
2

gaia-qa-tests

Generate QA tests and machine-readable verdicts for user stories.

Official
Advanced
deandumdeandum
3

testing

Plan testing strategies for unit, integration, and end-to-end layers.

Community
Advanced
OmerFarukOrucOmerFarukOruc
2

qa-only

Identify and report QA findings for web applications without applying fixes.

Community
Advanced