qa_fix

Fix QA issues from QA_SURVEY.md and update status.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/wesuuu/runbook --skill qa-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa_fix
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/qa_fix
Command: npx skills add https://github.com/wesuuu/runbook --skill qa-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA issues often lack consistent triage and rapid resolution. This Skill streamlines identifying, prioritizing, and patching issues documented in QA_SURVEY.md, with guidance for testing and status updates.

Core Features & Use Cases

  • Reads QA_SURVEY.md to enumerate open issues and their severities.
  • Allows selecting an issue by ID (e.g., QA-0003) or by priority (critical/high/medium/low).
  • Implements the fix following project conventions, writes or updates tests, and runs backend and frontend test suites.
  • Updates QA_SURVEY.md to reflect resolution and provide a concise summary.

Quick Start

Review QA_SURVEY.md, choose an issue to fix by ID or priority, implement the fix with tests, and update QA_SURVEY.md upon completion.

Frequently Asked Questions about qa_fix

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

FAQPage Schema
How do I fix QA issues documented in a survey markdown file?

You fix QA issues by reading the survey file, selecting issues by ID or priority, implementing the fix with tests, and updating the document. This workflow ensures consistent triage and rapid resolution across backend and frontend suites.

Can I prioritize bug fixes by severity level instead of issue ID?

Yes, you can prioritize bug fixes by severity level instead of issue ID. The system allows you to target a specific priority level like critical, high, medium, or low to systematically resolve the most urgent issues documented in your survey file.

What is the standard workflow for resolving tracked survey issues?

The standard workflow for resolving tracked survey issues involves reading the issue file, selecting a target by ID or priority, implementing the fix, writing or updating tests across backend and frontend, and finally updating the survey file to reflect the resolution status.

Do I need to manually update the QA survey file after fixing a bug?

No, you do not need to manually update the QA survey file after fixing a bug. The workflow enforces updating the survey document automatically upon completion to reflect the resolution and provide a concise summary of the applied fix.

What's the best way to automate issue tracking and bug fix updates?

The best way to automate issue tracking and bug fix updates is to use a command-driven workflow that reads your tracking file, applies fixes with corresponding tests, and writes the resolution status back to the document, ensuring rapid and consistent patching.