self-heal

Diagnose deployment failures, apply fixes, and redeploy up to three times.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nixopus/agent --skill self-heal-nixopus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: self-heal
Source: https://github.com/nixopus/agent/tree/main/skills/self-heal
Command: npx skills add https://github.com/nixopus/agent --skill self-heal-nixopus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Self-heal provides an automated remediation loop for failed deployments, diagnosing issues, applying fixes, and redeploying up to three times to restore healthy deployments.

Core Features & Use Cases

  • Automated failure diagnosis: reads deployment logs and known patterns to identify root causes.
  • Deterministic remediation: applies fixes in defined sequences and redeploys after each fix.
  • Escalation and rollback: if all attempts fail, escalates to a human operator or rolls back to the previous stable state.
  • GitHub-specific flow: for GitHub-based deployments, coordinates fixes via PRs when needed and avoids disrupting repository state.

Quick Start

Trigger the self-heal workflow when a deployment fails to diagnose, fix, and redeploy up to three times.

Frequently Asked Questions about self-heal

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

FAQPage Schema
How do I automate failed deployment remediation with rollback?▼

Automated failed deployment remediation uses a self-heal loop to diagnose issues, apply fixes, and redeploy up to three times. If all attempts fail, it escalates to a human operator or rolls back to the previous stable state.

What is the best way to diagnose and fix build failures automatically?▼

Diagnosing and fixing build failures automatically requires reading deployment logs and matching known patterns to identify root causes. The system then applies deterministic fixes from a deploy-patterns knowledge base before redeploying.

Does automated self-healing work with non-GitHub deployment sources?▼

Automated self-healing works with both GitHub and non-GitHub deployment sources. For GitHub-based deployments, it coordinates fixes via pull requests to avoid disrupting repository state.

What happens when automated deployment fixes fail after multiple attempts?▼

When automated deployment fixes fail after three attempts, the system follows explicit escalation decision paths. It either escalates the issue to a human operator or rolls back to the previous stable deployment state.

How do I safely apply fixes to GitHub deployments without disrupting repository state?▼

To safely apply fixes to GitHub deployments without disrupting repository state, the system coordinates remediation via pull requests. This ensures deterministic flow control while maintaining repository integrity during the self-heal process.

When should I use automated deployment rollback instead of manual intervention?▼

Automated deployment rollback should be used when a self-heal loop exhausts its three remediation attempts. The system applies knowledge-based fixes before triggering a safe rollback or escalation to avoid prolonged downtime.