bug-fix-expert

Automate bug identification, verification, fixing, and review with multi-agent collaboration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses software defects by first confirming their existence through rigorous multi-angle verification, then implementing a safe and tested fix, and finally ensuring quality through isolated review and security checks.

Core Features & Use Cases

  • Bug Confirmation: Proves bugs are real using multiple methods (runtime, tests, static analysis).
  • Safe Fixing: Implements fixes with comprehensive tests, ensuring code coverage and preventing regressions.
  • Isolated Review: Guarantees fixes are reviewed by a separate agent for correctness, security, and maintainability.
  • Use Case: When a user reports a critical production bug, this Skill will systematically reproduce it, apply the minimal necessary fix, add tests to prevent recurrence, and have the fix independently reviewed before deployment.

Quick Start

Use the bug-fix-expert skill to fix the bug reported in issue BUG-123.

Frequently Asked Questions about bug-fix-expert

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

FAQPage Schema
How do I systematically fix a critical production bug without introducing regressions?

To fix a critical production bug without regressions, first confirm the defect through cross-validation, implement the minimal necessary fix, add tests for coverage, and perform an isolated review. This ensures safety by verifying the bug exists before patching and checking code quality independently.

What is the best way to verify a software bug exists before attempting a fix?

The best way to verify a software bug exists is through multi-angle confirmation using runtime checks, tests, and static analysis. Cross-validation proves the bug is real and prevents wasted effort on non-reproducible issues before applying any code changes.

How do you ensure code quality and security when applying bug fixes?

To ensure code quality and security during bug fixes, enforce mandatory testing and code coverage alongside isolated code review and security checks. Having a separate agent review the patch independently guarantees correctness and maintainability before deployment.

Can I handle parallel development safely when fixing bugs of varying severity levels?

Yes, you can handle parallel development safely by enforcing strict Git operation protocols and worktree isolation. This approach supports P0 to P3 severity levels with adaptive response strategies, preventing branch conflicts while addressing multiple issues concurrently.

Does multi-agent collaboration improve software debugging and code review?

Multi-agent collaboration improves software debugging and code review by automating bug identification, implementing fixes with mandatory testing, and assigning a separate agent to review code for correctness and security. This isolated review process maintains high software quality.