self-healing
Self-healing codebase system. Monitors runtime errors, test failures, and build breaks. Automatically diagnoses root cause, generates fix, validates fix, and applies if safe. Zero human intervention for routine failures.
npx skills add vibeeval/vibecosystem --skill self-healing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Self-Healing Codebase Automated fault detection and repair. When a test fails, a build breaks, or a runtime error is logged, the healing pipeline wakes up, finds the root cause, generates a minimal fix, validates it, and applies it -- all without human intervention, as long as confidence is above the safety threshold. ## Trigger Conditions The healing pipeline activates on any of these events: | Trigger | Signal | Source | |---------|--------|--------| | Test failure | Any test exits non-zero | CI logs, `npm test` output | | Build break | Compiler/bundler error | CI logs, `npm run build` output | | Runtime error | Unhandled exception, 5xx response | Application logs, Vercel logs | | Type error | `tsc --noEmit` fails | Pre-commit hook, CI | | Lint failure | ESLint/Prettier error blocking CI | CI logs | ### Signals NOT Handled The following always require human review -- do NOT auto-heal: - Security vulnerabilities (auth bypass, injection, XSS) - Database migrations (schema changes, data loss risk) - Dependency version conflicts (breaking API changes) - Flaky tests (non-deterministic failures -- use `replay` agent instead) ## The 4-Phase Healing Pipeline ``` DETECT -> DIAGNOSE -> F
- Trigger Conditions
- Signals NOT Handled
- The 4-Phase Healing Pipeline
- Phase 1: Detect
- Phase 2: Diagnose
- Phase 3: Fix
- Phase 4: Validate
- Safety Rules
- Agent Roles
- Healing Log Format
- Metrics
- Key Metrics Defined
- Scope Limits (Non-Negotiable)
- Activation
git stash push -u -m "self-healing: pre-fix stash for <error-id>" For test failures: run the specific failing test + its file's full suite npm test -- --testPathPattern="<failing-file>" For build breaks: re-run the build npm run build For type errors: re-run type check npx tsc --noEmit For runtime errors: run integration tests if available npm run test:integration
What does the self-healing skill do?
Self-healing codebase system. Monitors runtime errors, test failures, and build breaks. Automatically diagnoses root cause, generates fix, validates fix, and applies if safe. Zero human intervention for routine failures.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill self-healing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.