fix

Orchestrate bug investigation, implementation, testing, and commit workflows.

8|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill fix-scooter-lacroix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/meta/fix
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill fix-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the entire bug resolution process, from initial investigation and diagnosis to implementing a fix, writing tests, and committing the changes.

Core Features & Use Cases

  • Automated Bug Resolution: Orchestrates a multi-step workflow to address software bugs efficiently.
  • Scope-Based Workflows: Adapts its process based on the type of issue (bug, hook, dependency, PR comments).
  • Risk Mitigation: Includes a premortem phase to identify potential risks before implementation.
  • Use Case: When a user reports a bug, they can invoke /fix bug and the Skill will automatically investigate logs, diagnose the root cause, propose a fix, and guide the user through implementation and testing.

Quick Start

Use the fix skill to debug and resolve the current bug.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I debug and fix code errors automatically?

To debug and fix code errors automatically, you can use an orchestrated workflow that investigates logs, diagnoses the root cause, proposes a fix, and guides you through implementation and testing.

How do I resolve PR review comments and address hook failures in my workflow?

Resolving PR review comments and hook failures is handled by routing to specialized agents that adapt the bug fixing process based on the specific issue scope, ensuring targeted resolution.

Do I need to manually write tests after implementing a bug fix?

You do not need to manually write tests after a bug fix if you use a comprehensive resolution workflow, which orchestrates writing tests and committing the code changes as part of its process.

What is the best way to prevent regressions when fixing software bugs?

The best way to prevent regressions when fixing software bugs is to use a workflow with a premortem phase for risk mitigation, identifying potential risks before implementation begins.

Does dependency error resolution require a different workflow than general bugs?

Dependency error resolution does not require a separate workflow; it uses scope-based workflows that adapt the investigation, implementation, and testing process specifically for dependency-related issues.

When should I not use an automated bug fixing workflow?

You should not use an automated bug fixing workflow when you need to bypass user checkpoints, as the process includes integrated risk assessment and requires user approval before committing code changes.