heal

Diagnose Claude Code session incidents and execute corrective actions.

1|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/hgflima/loopy --skill heal-hgflima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heal
Source: https://github.com/hgflima/loopy/tree/main/.claude/skills/heal
Command: npx skills add https://github.com/hgflima/loopy --skill heal-hgflima

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The 'heal' Skill addresses post-incident analysis in Claude Code sessions, enabling quick diagnosis, corrective action, and structured changelog persistence to prevent recurrence.

Core Features & Use Cases

  • Post-Mortem Analysis: Diagnose incidents by mining conversation history for root causes.
  • Corrective Actions: Formulate and execute fixes on skills, rules, and CLAUDE.md files.
  • Structured Changelog: Create a changelog for incident context and future analysis.
  • Use Case: After a user reports an error in a Claude Code session, the 'heal' Skill can analyze the incident, propose a fix, and execute it, then log the event for future reference.

Quick Start

Use the heal skill to analyze the incident reported in the current session and apply the proposed fix.

Frequently Asked Questions about heal

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

FAQPage Schema
How do I perform a post-mortem analysis on a Claude Code session incident?

Post-mortem analysis diagnoses Claude Code session incidents by mining conversation history for root causes. The skill uses agents to formulate solutions, execute corrective actions on skills and rules, and persist an audit trail.

Can I automate self-healing fixes for errors in CLAUDE.md files?

Yes, self-healing fixes for CLAUDE.md files are automated by analyzing the conversation history to formulate a corrective action. Agents execute the proposed fix and update the changelog to prevent future recurrence.

What is the best way to log root-cause incident analysis results for future reference?

Logging root-cause incident analysis results is handled by creating a structured changelog. This persists the incident context, executed corrective actions, and audit information, providing a reference for future analysis and prevention.

Do I need additional dependencies to run incident-analysis and corrective actions?

No additional dependencies are required to run incident-analysis and corrective actions. The skill operates independently using its internal scripts, references, and assets to diagnose issues and execute fixes.

What limitations exist when applying corrective actions to Claude Code session incidents?

Limitations include relying entirely on available conversation history for root-cause identification. Corrective actions target skills, rules, and CLAUDE.md files, meaning unresolved external dependencies outside the session cannot be self-healed.

Does the heal skill support collaborative review before executing session fixes?

Yes, collaborative review is supported before executing session fixes. The skill's agents perform root cause analysis and solution formulation, followed by a collaborative review phase before any corrective action is applied to the environment.