healer

Automate bug fixing via TDD red-green cycle and update report status.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/moongci38-oss/forge-plugins --skill healer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healer
Source: https://github.com/moongci38-oss/forge-plugins/tree/main/forge-build/skills/healer
Command: npx skills add https://github.com/moongci38-oss/forge-plugins --skill healer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the bug fixing process based on bug reports, following the TDD red-green cycle and updating the report status to 'Fixed'. It triggers automated fixes after reproduction, root cause analysis, and code modification, followed by verification and regression test automation.

Core Features & Use Cases

  • Automated Bug Fixing: Executes TDD red-green cycle (reproduction, root cause analysis, surgical modification, code review, verification, regression test automation) based on bug reports.
  • Report Status Update: Updates the report status to 'Fixed' after successful automated fixes.
  • Use Case: When a bug report is written and the developer wants to start the bug fixing process, they can use this Skill to automate the fixing process.

Quick Start

Use the '/healer BUG-NNN' command to trigger the bug fixing process for the bug report with ID 'BUG-NNN'.

Frequently Asked Questions about healer

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

FAQPage Schema
How do I automate bug fixing from a bug report using TDD?

Automated bug fixing using TDD parses bug reports to reproduce failures, analyzes root causes, modifies code, and runs regression tests. It follows the red-green cycle to verify fixes before updating the report status to Fixed.

What is the TDD red-green cycle for code modification?

The TDD red-green cycle for code modification is an automated process that reproduces a bug, analyzes the root cause, surgically modifies the code, and verifies the fix through automated regression testing.

Do I need a specific bug report format to trigger automated bug fixing?

Automated bug fixing requires access to bug report files and the project codebase. You trigger the process by passing the bug report ID, which the Skill parses to execute the TDD red-green cycle and update the status.

How does automated code review work during TDD regression test automation?

Automated code review during TDD regression test automation happens after surgical code modification. The Skill executes a verification step to ensure the bug fix passes the red-green cycle and updates the report status upon success.

Can I update bug report status automatically after code modification?

Updating bug report status automatically after code modification is a core feature. Once the TDD red-green cycle successfully verifies the fix and completes regression test automation, the report status is updated to Fixed.

What are the limitations of automated root cause analysis for bug fixing?

Automated root cause analysis for bug fixing requires direct access to both the bug report files and the project codebase. It is limited to executing the TDD red-green cycle and cannot resolve bugs without explicit reproduction steps.