fixme-task

Orchestrate config-driven bug-fix pipelines by dispatching phase skills and aggregating outputs.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/denis-pingin/fixme --skill fixme-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixme-task
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-task
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end, config-driven bug-fix pipelines by coordinating plan, execution, and review steps without performing code changes itself.

Core Features & Use Cases

  • Dispatches each phase's skills according to a .fixme/config.json pipeline, enabling repeatable, auditable bug-fix workflows.
  • Manages integrated review loops, decision logging, and optional ticket state transitions through the fixme-tickets abstraction.
  • Retains full task context across iterations, ensuring no loss of information as plans are refined and changes validated.

Quick Start

Describe the task you want fixed and the pipeline you want to run, then invoke /fixme-task to start execution.

Frequently Asked Questions about fixme-task

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

FAQPage Schema
How do I automate bug-fix pipelines with end-to-end orchestration?

Automate bug-fix pipelines by dispatching phase skills according to a .fixme/config.json configuration, aggregating outputs into a coherent plan. The orchestrator coordinates plan, execution, and review steps while retaining full task context across iterations.

Can I use custom named pipelines for bug-fix workflows?

Custom named pipelines are supported for bug-fix workflows through definitions in .fixme/config.json. You can define both default and named pipelines to enable repeatable, auditable task execution tailored to specific routing and review requirements.

How does ticket state transition work in a bug-fix workflow?

Ticket state transitions are optionally coordinated via the fixme-tickets abstraction during bug-fix workflows. The orchestrator routes findings through designated review and handler loops, logging decisions and updating ticket states as the pipeline progresses.

Do I need a config file to run automated bug-fix workflows?

A config file is not strictly required to run automated bug-fix workflows. The orchestrator supports pipelines defined in .fixme/config.json but can also fall back to hardcoded defaults to dispatch phase skills if no configuration is provided.

Why does the orchestrator avoid reading source code directly during bug-fix execution?

The orchestrator avoids reading source code directly to enforce strict context retention and maintain separation of concerns. It routes all findings through designated review and handler loops, ensuring phase skills handle execution while the orchestrator aggregates outputs.

What are the limitations of using an orchestrator for bug-fix pipelines?

A key limitation is that this orchestrator performs no code changes itself, relying entirely on dispatched phase skills for execution. It is constrained by the pipeline definitions in .fixme/config.json and requires designated review loops to validate changes before completion.