heal-until-green

Automates diagnosing and iteratively fixing failing tests until they pass.

Updated Aug 27, 2026

Search Tags:#automation #testing #debugging #bug fixing #test suite

Ready to run

npx skills add https://github.com/adamway/thoughts-cli --skill heal-until-green

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heal-until-green
Source: https://github.com/adamway/thoughts-cli/tree/main/.claude/skills/heal-until-green
Command: npx skills add https://github.com/adamway/thoughts-cli --skill heal-until-green

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of diagnosing and fixing failing tests, saving developers time and effort in manual debugging.

Core Features & Use Cases

Automated Failure Diagnosis: Reads failing test reports and isolates root causes.
Iterative Fixing: Proposes minimal code changes to fix each failure, re-running tests after each attempt.
Regression Protection: Ensures that fixes do not introduce new failures by re-running the full test suite.
Use Case: Ideal for developers working on large test suites who want to quickly repair flaky or broken tests without manual trial and error.

Quick Start

Invoke the heal-until-green skill for your project, providing the failing test details and allowing it to iteratively fix the issues until all targeted tests pass or it encounters irrecoverable failures.

Frequently Asked Questions about heal-until-green

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

FAQPage Schema

How do I automate fixing failing tests in my software project?▼

Automated test fixing works by reading failing test reports, isolating root causes, and proposing minimal code changes iteratively. It re-runs tests after each attempt to verify fixes and ensure regression detection without manual trial and error.

Can I use automated debugging for continuous integration test failures?▼

Automated debugging is ideal for continuous integration scenarios requiring minimal human intervention. It diagnoses failing tests, proposes iterative fixes, and re-runs the full test suite to ensure regression detection and prevent new failures from being introduced.

What is the best way to repair flaky tests without skipping assertions?▼

The best way to repair flaky tests without skipping assertions is using iterative automated fixing that prevents weakening assertions or skipping tests. It proposes minimal code changes and re-runs the full test suite to ensure fixes do not introduce new failures or weaken existing assertions.

Does automated test fixing work with test-driven development workflows?▼

Automated test fixing works directly with test-driven development by diagnosing failing tests and proposing minimal code changes. It iteratively fixes failures, re-running tests after each attempt to ensure regression detection and maintain test suite health without weakening assertions.

How do I restore test suite health after multiple test failures?▼

Restoring test suite health involves automated failure diagnosis that reads failing test reports and isolates root causes. It then proposes minimal code changes iteratively, re-running the full test suite after each attempt to ensure regression protection and prevent new failures.

Why does automated bug fixing prevent weakening assertions during test repair?▼

Automated bug fixing prevents weakening assertions by enforcing regression detection during iterative fixes. It re-runs the full test suite after each minimal code change, ensuring tests pass legitimately without skipping assertions or introducing new failures into the test suite.