fixing

Automate bug-fix workflows with subagents for debugging, analysis, and verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill fixing-bonethedeveloper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing
Source: https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book/tree/main/.claude/skills/fixing
Command: npx skills add https://github.com/BoneTheDeveloper/Electronic-Contact-Contact-Book --skill fixing-bonethedeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates complex bug-fix workflows by orchestrating debugging, analysis, and verification across codebases.

Core Features & Use Cases

  • Intelligent mode selection and routing to choose Autonomous, HITL, or Quick workflows based on issue type.
  • Complexity-aware branching that routes to the appropriate workflow (quick fixes, standard fixes, or deep investigations).
  • Parallel exploration and multi-agent coordination (debugging, Explore, Bash, researcher, planner, tester, code-reviewer) with reference-guided steps.
  • Guided per-issue templates (CI/CD failures, type errors, test failures, UI bugs) and on-demand resource loading from references.

Quick Start

Initiate an autonomous fix plan by assessing the issue, selecting the appropriate workflow, and starting debugging, implementation, and verification steps.

Frequently Asked Questions about fixing

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

FAQPage Schema
How do I automate complex multi-file bug fixes across a codebase?

Multi-file bug fixes are automated by orchestrating debugging, analysis, and verification. The system selects an appropriate workflow, performs parallel exploration, and coordinates subagents to resolve cross-cutting issues.

Can I automatically debug and fix CI/CD pipeline failures?

Yes, CI/CD failures can be debugged and fixed automatically. The workflow uses guided templates for CI/CD failures, assesses complexity, and routes the issue to specialized subagents for structured resolution.

What is the best way to find the root cause of a cross-cutting software bug?

Finding a root cause for cross-cutting bugs requires parallel exploration and multi-agent coordination. The system deploys debugging and researcher subagents to investigate the codebase and identify the underlying issue.

Does this bug fixing workflow support human-in-the-loop mode?

Yes, the workflow supports human-in-the-loop mode. Intelligent mode selection evaluates the issue type and chooses between Autonomous, HITL, or Quick workflows to match the required level of oversight.

How do I verify code changes after implementing a complex fix?

Code changes are verified through guided verification steps using subagents like tester and code-reviewer. This ensures the implementation resolves the original issue without introducing regressions across the codebase.

When should I use a quick fix workflow versus a deep investigation for debugging?

Complexity-aware branching determines whether to use a quick fix or deep investigation. The system assesses the issue and routes simple errors to quick workflows while directing cross-cutting bugs to standard or deep investigations.