fix-failures

Identify and resolve CI check failures from current branch evidence.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/alexandersumer/config --skill fix-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-failures
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/fix-failures
Command: npx skills add https://github.com/alexandersumer/config --skill fix-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of identifying and fixing real check failures from various sources, such as arguments, pasted errors, local checks, or CI systems.

Core Features & Use Cases

  • Proof Policy: Implements a strict proof policy to reuse evidence only when valid and to execute the narrowest checks needed.
  • Resolve the Target: Determines the scope of the failure by inspecting repository and SCM context, including current branch, recent commits, and check status.
  • Triage from Evidence: Captures failing signals and triages multiple failures based on root causes.
  • Fix Constraints: Enforces strict constraints on fixing the root cause without patching symptoms or suppressing errors.
  • Verify: Reruns targeted checks and compares signals to ensure the fix is effective.

Quick Start

Use the fix-failures skill to identify and fix a failure in your current branch's CI/check.

Frequently Asked Questions about fix-failures

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

FAQPage Schema
How do I resolve real check failures in my current branch's CI?

To resolve CI check failures, inspect the current branch status, recent commits, and pasted errors to identify root causes, then run targeted checks to verify the fix without suppressing errors.

What is the best way to triage multiple code debugging failures by root cause?

Triage multiple failures by capturing failing signals from local checks or CI systems, grouping them by root cause, and enforcing strict constraints to fix the core issue rather than patching symptoms.

How does root cause analysis handle CI troubleshooting without impacting system integrity?

Root cause analysis ensures minimal system impact by executing the narrowest checks needed and reusing valid evidence only, enforcing a strict proof policy throughout the debugging workflow.

Can I fix pasted errors and local check failures using automated failure resolution?

Yes, failure resolution supports arguments, pasted errors, local checks, and CI systems by determining failure scope through repository and SCM context inspection before applying fixes.

Why does failure resolution enforce strict proof policies during software quality debugging?

Failure resolution enforces strict proof policies to ensure fixes target the actual root cause and verify effectiveness by rerunning targeted checks and comparing signals, preventing symptom patching.