fix

Diagnose and fix root-cause issues across data pipelines, app stacks, and infrastructure.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill fix-vanducng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/vanducng/skills/tree/main/skills/fix
Command: npx skills add https://github.com/vanducng/skills --skill fix-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end fixing across surfaces you actually work on: data pipelines, app stack, and infra. Scout → diagnose → apply at root cause → verify with fresh evidence → add regression guard. Use for failing DAGs, dbt test failures, 5xx, UI regressions, GH Actions failures, terraform drift, CrashLoopBackOff, lint/type errors. Stops after 3 failed attempts to question architecture.

Core Features & Use Cases

Iron law: NO FIX WITHOUT ROOT CAUSE. NO "DONE" WITHOUT FRESH EVIDENCE.

  • Scout and diagnose: locate the root cause with structured evidence and a minimal blast radius.
  • Multi-surface governance: apply fixes across data, app, and infra with regression prevention.
  • Verification discipline: re-run exact failing steps, sweep blast radius, and document contracts.

Quick Start

Initiate the diagnostic loop by scouting the codebase, then proceed through diagnosis and verification to land a minimal root-cause fix.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I diagnose and fix failing dbt tests or DAG failures end-to-end?

To fix DAG failures and dbt tests end-to-end, you must scout the codebase to locate the root cause with structured evidence, apply a minimal fix, and verify by re-running the exact failing steps with fresh evidence.

What is the best way to resolve 5xx errors and UI regressions without masking the root cause?

Resolving 5xx errors and UI regressions requires a strict root-cause approach: diagnose with structured evidence, apply multi-surface governance fixes, and verify the resolution with fresh evidence before adding regression prevention.

How do I fix infrastructure drift and CrashLoopBackOff errors across my app stack?

Fixing infra drift and CrashLoopBackOff errors involves scouting the infrastructure, diagnosing the root cause with a minimal blast radius, applying the fix, and verifying the resolution with fresh evidence.

Does this approach work for resolving lint, type errors, and GitHub Actions failures?

Yes, this approach applies to lint, type errors, and GitHub Actions failures by diagnosing the root cause, applying the fix across surfaces, and verifying the resolution with fresh evidence and regression guards.

What happens if I cannot find the root cause after multiple debugging attempts on my data pipeline?

If debugging your data pipeline fails after three attempts, the process stops to question the underlying architecture, preventing repeated ineffective fixes and ensuring you reassess the system design.

Can I use this method to fix terraform drift across multiple infrastructure surfaces?

Yes, you can fix terraform drift across infrastructure surfaces by scouting for the root cause, applying multi-surface governance fixes, and verifying the resolution with fresh evidence and regression prevention.