conductor-defect

Automate end-to-end bug fixing from BUG.md across versions and modules.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill conductor-defect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor-defect
Source: https://github.com/rashidee/co2-skills/tree/main/skills/conductor-defect
Command: npx skills add https://github.com/rashidee/co2-skills --skill conductor-defect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes bugs reported by humans by analyzing a BUG.md, organizing bugs by version and module, and coordinating end-to-end fixes across versions using Ralph Loop, Playwright-based repro, and artifact updates (BUG_MASTER.md, BUG_TEST_SPEC.md, BUG_FIX_PLAN.md).

Core Features & Use Cases

  • Tagging and tracking bugs across versions with a central BUG_MASTER.md, including per-version and per-module organization.
  • Sequential version processing: resolve all bugs for version N before starting N+1, with reproducibility validation and test artifact generation.
  • Ralph Loop integration to manage iterative bug-fixing sessions and ensure progress continuity across sessions.

Quick Start

Invoke the skill by providing an application name and optional version and module to start an automated bug-fix session.

Frequently Asked Questions about conductor-defect

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

FAQPage Schema
How do I automate end-to-end bug fixing from a markdown bug report?

Automating bug fixing from a BUG.md file involves parsing the markdown report, organizing issues by version and module, and coordinating sequential fixes using Ralph Loop. The workflow generates tracking artifacts like BUG_MASTER.md and a bug fix plan to drive end-to-end resolution.

How do I track bug fixes across multiple software versions and modules?

Tracking bugs across versions and modules requires a centralized BUG_MASTER.md artifact. The workflow processes versions sequentially, resolving all bugs for version N before starting N+1, while validating reproducibility and generating test specifications for each module.

Do I need Playwright to reproduce bugs in an automated fixing workflow?

Yes, Playwright is required to reproduce bugs during the automated fixing workflow. The skill uses Playwright-based reproduction to validate that reported issues in BUG.md actually exist before attempting fixes and generating test artifacts.

What is the Ralph Loop for iterative bug fixing sessions?

The Ralph Loop is a progress persistence mechanism that manages iterative bug-fixing sessions. It ensures progress continuity across multiple sessions, allowing you to pause and resume end-to-end bug resolution without losing track of completed fixes or pending tasks.

Can I fix bugs sequentially by version using a markdown tracking system?

Yes, sequential version processing resolves all bugs for version N before starting N+1. The system uses BUG.md input, applies module filters, and creates BUG_MASTER.md, BUG_TEST_SPEC.md, and BUG_FIX_PLAN.md artifacts to organize and drive the markdown tracking workflow.

What context data do I need in CLAUDE.md to run automated bug fixes?

CLAUDE.md must contain context data including paths and credentials required by the bug fixing workflow. This context data allows the automated system to access project resources, reproduce bugs with Playwright, and update tracking artifacts across versions and modules.