fixing

Diagnose and fix bugs, test failures, and CI/CD issues across codebases.

Updated Jun 16, 2025
One-click install
npx skills add https://github.com/Stonelukas/Mouse-on-Numpad --skill fixing-stonelukas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing
Source: https://github.com/Stonelukas/Mouse-on-Numpad/tree/main/.opencode/skill/fixing
Command: npx skills add https://github.com/Stonelukas/Mouse-on-Numpad --skill fixing-stonelukas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fixing complex software issues across projects by orchestrating debugging, root cause analysis, and automated verification with intelligent routing.

Core Features & Use Cases

  • End-to-end workflow orchestration for bug fixes across codebases.
  • Mode-based routing: autonomous, human-in-the-loop, and quick fixes to match urgency.
  • Parallel exploration and automated verification with subagents and references.
  • Structured collaboration with code-review, git-manager, and docs updates when needed.
  • Reusable templates for CI/CD issues and UI/backend bugs.

Quick Start

Initiate a fixing workflow on an issue by selecting a mode and following the guided steps to diagnose, fix, test, and review.

Frequently Asked Questions about fixing

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

FAQPage Schema
How do I coordinate end-to-end bug fixes across multi-file codebases?

End-to-end bug fixes across multi-file codebases are coordinated using intelligent routing to streamline repair workflows. The process orchestrates structured steps for debugging, root cause analysis, implementation, testing, and code review by coordinating subagents and references.

What is the best way to automate CI/CD issue resolution and test failure debugging?

Automating CI/CD issue resolution and test failure debugging is handled through mode-based routing that offers autonomous, human-in-the-loop, or quick fix options. Reusable templates guide the structured diagnosis, parallel exploration, and automated verification of these specific issues.

Does this debugging workflow support both UI and backend components?

Yes, this debugging workflow supports both UI and backend components. It is suitable for single-file or multi-file issues across codebases, providing structured steps to diagnose, fix, test, and review errors regardless of the application layer.

Can I use human-in-the-loop control for complex code review and bug fixes?

Yes, you can use human-in-the-loop control for complex code review and bug fixes. Mode-based routing allows you to select autonomous, human-in-the-loop, or quick fix approaches, ensuring structured collaboration and oversight during the repair process.

When should I use parallel exploration for root cause analysis?

Parallel exploration for root cause analysis should be used when diagnosing complex, multi-file software issues. It allows subagents to investigate multiple potential causes simultaneously before planning the implementation and executing automated verification.

What are the limitations of using autonomous mode for code review and bug fixing?

Autonomous mode for code review and bug fixing lacks real-time human oversight, making it less suitable for sensitive or high-risk changes. For critical updates, using the human-in-the-loop mode ensures structured collaboration and manual approval during the debugging workflow.