bug-fix-expert

Coordinate multi-agent bug fixes with verification before code changes.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/unorouter/sub2api --skill bug-fix-expert-unorouter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix-expert
Source: https://github.com/unorouter/sub2api/tree/main/skills/bug-fix-expert
Command: npx skills add https://github.com/unorouter/sub2api --skill bug-fix-expert-unorouter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

以"先确认、再修复"的多智能体协作方式处理缺陷,保证速度与安全。

Core Features & Use Cases

  • 在独立工作区内进行缺陷复现、静态分析、修复与审查的端到端流程,提升修复效率并降低风险。
  • 引入多角色分工与信标机制,确保修复前有充分证据并由独立审查确认。
  • 支持严格的测试覆盖率和安全预检,确保改动的质量与安全性。

Quick Start

Initiate the bug-fix-expert workflow to coordinate verification, analysis, repair, and review stages.

Frequently Asked Questions about bug-fix-expert

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

FAQPage Schema
How do I automate multi-agent bug fixing to safely reproduce and repair code defects?

Automated multi-agent bug fixing orchestrates verification, analysis, repair, and independent review stages within isolated worktrees to safely reproduce and resolve code defects. Strict safety gates and 85% test coverage ensure reliable outcomes.

What is the best way to verify a software defect exists before applying code changes?

Defect verification before code changes requires a strict workflow that confirms the defect through reproduction and static analysis in an isolated worktree. Independent multi-agent reviews and safety gates enforce this confirmation before any repair.

How does isolated worktree bug repair prevent risks during CI and production issue resolution?

Isolated worktree bug repair prevents risks by separating defect reproduction, repair, and review stages from the main branch. Imposing strict workflow steps, safety gates, and 85% test coverage ensures changes remain safe for CI and production.

Can I use multi-agent code review to enforce test coverage and quality assurance for bug fixes?

Multi-agent code review enforces quality assurance by coordinating independent reviews and imposing strict 85% test coverage requirements. Completion beacons signal that all safety gates and verification steps are fully satisfied.

Does the bug-fix workflow require dependencies to handle code reviews and CI production issues?

The bug-fix workflow operates without external dependencies, handling CI, code review, and production issues natively. It uses internal multi-agent coordination and isolated worktrees to manage the entire verification and repair process.

Why should I use a multi-agent workflow for bug fixing instead of standard manual code repair?

A multi-agent workflow separates verification, analysis, repair, and review into distinct roles, ensuring defects are confirmed before changes. This approach imposes strict safety gates and 85% test coverage, reducing risks common in manual code repair.