heal

Diagnose GitHub Actions CI failures and propose reproducible repairs.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill heal-0xharbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heal
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/heal
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill heal-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI failures block progress in automated pipelines; this Skill provides a self-healing workflow that diagnoses failures, classifies them, and either auto-fixes mechanical issues or escalates with a structured diagnosis.

Core Features & Use Cases

  • Automated failure acquisition and classification for lint, build, test, and deployment steps.
  • Auto-fix capabilities where safe (lint, dependency issues) and escalation for non-mechanical failures.
  • Guidance and reproducible steps for developers to verify and re-run pipelines across branches.

Quick Start

Paste CI failure output to start interactive healing, or pass a GitHub Actions run URL with --ci to fetch results, or enable --auto to auto-fix and push changes.

Frequently Asked Questions about heal

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

FAQPage Schema
How do I automatically diagnose and fix GitHub Actions CI failures?

To automatically diagnose and fix GitHub Actions CI failures, you can use a self-healing automation skill that parses failure outputs, classifies them into categories like LINT or BUILD, and executes safe automated fixes when permitted.

What types of continuous integration errors can be auto-fixed in a pipeline?

In a continuous integration pipeline, mechanical errors such as lint failures and dependency issues can be auto-fixed safely, while non-mechanical failures receive a structured diagnosis and escalation for manual intervention.

How does CI failure classification work for automated pipeline repairs?

CI failure classification works by parsing failure outputs from pipeline steps like test or deployment and mapping them to specific categories such as LINT, BUILD, or IMPORT to determine if a safe, reproducible repair can be executed.

Can I fetch GitHub Actions run results directly to diagnose CI failures?

Yes, you can fetch GitHub Actions run results directly to diagnose CI failures by passing a GitHub Actions run URL with the appropriate command flag, or by pasting the failure output to start interactive healing.

When should I not use automated self-healing for CI pipeline failures?

You should not use automated self-healing for non-mechanical CI pipeline failures, as these issues cannot be safely auto-fixed and instead require structured diagnosis, developer guidance, and manual verification across branches.