self-healing

Run two-cycle stress reviews with targeted worker corrections for unresolved defects.

13|5|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Jonghakseo/my-pi --skill self-healing-jonghakseo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-healing
Source: https://github.com/Jonghakseo/my-pi/tree/main/skills/self-healing
Command: npx skills add https://github.com/Jonghakseo/my-pi --skill self-healing-jonghakseo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces defects and unresolved risks by coordinating repeated stress reviews with narrowly scoped worker fixes instead of relying on a single implementation pass.

Core Features & Use Cases

  • Two-Cycle Review Loop: Runs stress-interview and worker correction cycles exactly twice, preventing uncontrolled iteration.
  • Actionable Triage: Classifies findings by priority and fix class, automatically addressing reproducible issues while escalating judgment-dependent risks.
  • Scope Control: Limits worker changes to concrete, high-value issues and records unresolved risks after the loop.
  • Use Case: Apply it after a complex multi-file change to expose correctness gaps, implement targeted fixes, and document remaining risks before final review.

Quick Start

Ask the self-healing skill to run its two-cycle stress-review and targeted-fix workflow for the specified implementation or task.

Frequently Asked Questions about self-healing

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

FAQPage Schema
How do I expose correctness gaps after a complex multi-file change?

Iterative stress reviews expose correctness gaps in complex multi-file changes by applying repeated stress-interview cycles, followed by targeted worker corrections to stabilize the implementation.

What is the best way to automate code correction for unresolved defects?

Automated code correction for unresolved defects is best handled by an iterative review loop that applies stress testing, triages findings by priority, and executes narrowly scoped worker fixes.

How does stress testing work with iterative code review?

Stress testing in iterative code review works by running stress-interview and worker correction cycles exactly twice, automatically addressing reproducible issues while escalating judgment-dependent risks to prevent uncontrolled iteration.

How many review cycles are needed for pre-review quality checks on multi-file changes?

Pre-review quality checks on multi-file changes require exactly two review cycles, strictly limiting iteration to prevent uncontrolled loops while ensuring actionable items are triaged and scope-controlled fixes are applied.

How do I triage and document remaining risks after stress testing code?

Triage and document remaining risks after stress testing by classifying findings by priority and fix class, automatically addressing reproducible issues, and explicitly reporting unresolved judgment-dependent risks when the review loop ends.

Can I use subagents to triage actionable items during code correction?

Yes, you can use Pi subagent tool calls to triage actionable items during code correction, automatically addressing reproducible issues while escalating judgment-dependent risks and limiting scope-controlled fixes to high-value defects.