repair

Repair scoped QA failures and rerun affected test items.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill repair-edonghyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repair
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/qa-operator/skills/repair
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill repair-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you fix scoped, reproducible defects discovered during QA and immediately verify the result, reducing the time spent on manual back-and-forth between triage, code changes, and retesting.

Core Features & Use Cases

  • Scoped bug repair: Makes the smallest safe code change needed for a clearly reproduced local defect.
  • Retest and evidence update: Reruns the affected QA item, captures after evidence, and updates the result records.
  • Controlled repair workflow: Supports proposal-only review or auto-local repair when the user explicitly permits code changes.
  • Use case: A QA pass flags a failing local screen flow with a clear expected result; this Skill repairs the defect, reruns the item, and records the outcome.

Quick Start

Use the repair skill to fix the verified local QA defect, rerun the affected item, and update the repair log and QA results.

Frequently Asked Questions about repair

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

FAQPage Schema
How do I fix verified QA bugs and rerun the affected tests?

To fix verified QA bugs, this Skill applies minimal safe code edits to the scoped local defect, reruns the affected browser or test items, and updates the QA results and repair log with the outcome.

Can I review code changes before a bug fix is applied?

Yes, you can use the proposal-only review workflow to evaluate the suggested code fix before permitting auto-local repair, ensuring you control all code changes during the bug-fix process.

How does retest evidence get updated after a browser-testing failure is repaired?

After repairing the browser-testing failure, the Skill reruns the affected QA item, captures the after evidence, and records the updated outcome in the qa-results for verification.

Does this automated repair workflow work with any QA testing tool?

This workflow specifically handles verified defects found by qa-operator during local browser-testing, requiring claim tracking and reproducible failures to execute its automated retest loops safely.

Why are minimal safe edits important for local QA defect repair?

Minimal safe edits ensure that bug repair changes remain strictly scoped to the verified defect, preventing unintended side effects before rerunning the affected test items and updating the repair log.

What happens if the retest still fails after applying a code fix?

If the retest fails after the bug fix, the Skill updates the repair log and qa-results with the failed outcome, maintaining accurate claim tracking for the unresolved defect.