skill-repair

Diagnose failing skill scripts, propose fixes, and re-run original steps.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/shellicar/skills --skill skill-repair
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-repair
Source: https://github.com/shellicar/skills/tree/main/skills/skill-repair
Command: npx skills add https://github.com/shellicar/skills --skill skill-repair

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skills and automation workflows become unreliable when failing scripts or unclear instructions are worked around instead of fixed, causing silent divergence and recurring bugs. This Skill enforces a fix-and-retry discipline so that failures are diagnosed, corrected, and re-run, preserving deterministic workflows and auditability.

Core Features & Use Cases

  • Fix-first policy: Require explicit identification of the failing skill step, a proposed corrective change, and re-running the original skill instead of manual workarounds.
  • Failure reporting guidance: Standardizes how to report syntax errors, runtime errors, missing paths, or incorrect outputs so fixes are actionable.
  • Use Case: In a CI pipeline or developer workflow where a data-gathering script fails, follow the skill-repair steps to fix the script, validate output, and prevent ad-hoc bypasses that hide the bug.

Quick Start

When a skill script errors, describe the exact failure, propose a specific fix, apply the fix with confirmation if unsure, and re-run the original skill step.

Frequently Asked Questions about skill-repair

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

FAQPage Schema
How do I fix failing scripts in automated workflows instead of working around them?

To fix failing scripts in automated workflows, identify the exact failing step, propose a specific corrective change, apply the fix, and re-run the original skill step. This preserves deterministic behavior and prevents silent divergence or recurring bugs.

What is the best way to handle error-handling and unexpected output in CI pipelines?

Handling error-handling and unexpected output in CI pipelines requires standardizing failure reporting for syntax or runtime errors, proposing actionable fixes, and re-running the original steps. This enforces a fix-and-retry discipline that maintains workflow auditability and reliability.

Why does working around unclear instructions in devops scripts cause recurring bugs?

Working around unclear instructions in devops scripts causes recurring bugs because it hides the underlying failure, leading to silent divergence. Fixing the script directly and re-running the workflow preserves deterministic outputs and prevents hidden issues.

Does this fix-and-retry approach apply to human-augmented automation or only CI runs?

This fix-and-retry approach applies to both CI runs and human-augmented automation. Whenever scripts error, produce unexpected output, or instructions are unclear, it requires clear failure reporting, proposed fixes, and re-running the original skill steps to restore deterministic workflow behavior.

How do I report script failures so that workflow reliability fixes are actionable?

To report script failures so that workflow reliability fixes are actionable, standardize the reporting of syntax errors, runtime errors, missing paths, or incorrect outputs. Explicitly identify the failing skill step and propose a specific corrective change before re-running.

When should I not use a manual workaround for debugging broken automation scripts?

You should never use a manual workaround for debugging broken automation scripts when a script errors or produces unexpected output. Manual bypasses hide bugs and break deterministic workflow behavior; always apply a fix-and-retry discipline to validate output and restore reliability.