error-diagnose-fix

Diagnoses and fixes build and compilation errors through an iterative agent loop.

1.6k|73|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill error-diagnose-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-diagnose-fix
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.agents/skills/error-diagnose-fix
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill error-diagnose-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and compilation errors often trigger a slow ping-pong where the user pastes one error, the agent guesses a fix, and the build stays broken for many rounds. This Skill takes ownership of the whole process: it runs the build itself, collects all errors at once, finds root causes via dependency analysis, and loops until the build is green.

Core Features & Use Cases

  • Full error collection: Runs the build command (cargo, bun, expo) and parses every error into a structured list instead of fixing one at a time.
  • Root-cause analysis: Groups errors by file and crate, distinguishes root causes from cascading failures, and fixes root causes first.
  • Safe iterative loop: Creates git revert points before each fix, reverts failed hypotheses, tracks state across rounds, and escalates to the user when stuck.
  • Use Case: After an Expo or dependency upgrade breaks the build with 12 cascading TypeScript and Rust errors, the agent runs the build, identifies 2 root causes, fixes them in order, and reaches 0 errors in a few rounds without user involvement.

Quick Start

Ask the agent to run error-diagnose-fix on the failing build, for example by saying the build is broken and to fix all compilation errors.

Frequently Asked Questions about error-diagnose-fix

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

FAQPage Schema
How do I fix multiple cascading build errors at once?

Run the full build command and parse all errors into a structured list, then group them by file and dependency direction. Fix root causes such as changed type definitions or renamed modules first, since downstream cascade errors disappear once the upstream issue is resolved.

How to fix cargo workspace errors across multiple crates?

Use cargo tree to understand the dependency direction between crates, then fix errors in the most-upstream crate first. Many downstream errors resolve automatically after the upstream fix, leaving only independent errors to address.

What should I do when a framework upgrade breaks the build?

Check the migration guide for the upgraded framework using documentation tools like context7, review the changelog, and look for official codemods such as expo-doctor. Apply migration steps systematically rather than fixing errors one at a time.

When should I not use an automated build-fix loop?

Avoid it for runtime bugs where behavior is wrong but the build passes, CI-only failures that work locally, and single obvious typos. Those cases are better handled by debugging workflows or direct manual fixes.

Why does a fix sometimes make the build worse?

A wrong hypothesis can introduce new type mismatches or break additional call sites. The correct response is to revert immediately using the git checkpoint, record the failed hypothesis, and try a different approach instead of stacking more fixes.