build-fix-edho-ferdian

Diagnose and fix build, compile, and dependency failures across 17 language stacks with minimal verified diffs.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill build-fix-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-fix-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/build-fix-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill build-fix-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Build, compile, dependency-resolution, and startup failures block development, and fixing them often tempts quick suppressions (type ignores, fake migrations, silent version bumps) that hide the real cause. This Skill resolves such failures with the smallest honest diff, verified by re-running the actual build command. ## Core Features & Use Cases - Automatic stack detection and routing: Detects the toolchain from project files (package.json, go.mod, Cargo.toml, pubspec.yaml, .csproj, and more) and loads a matching diagnostic reference for 17 stacks including JavaScript/TypeScript, Django/Python, Go, Rust, Java/Spring, Kotlin, Swift, Flutter, .NET, C++, and Ruby. - Structured six-phase loop: Reproduce the exact error, classify it against diagnostic tables, read the affected file, apply one surgical fix at a time, verify by re-running the build, then report. - Anti-suppression reflection gate: Before reporting success, it checks for suppressed errors, widened types, unplanned dependency bumps, and unverified builds, reverting and escalating instead of reporting a false fix. - Use Case: A developer pastes a Gradle "Duplicate class" error or a Django "InconsistentMigrationHistory" traceback; the Skill identifies the error family from the stack-specific table, applies the minimal fix, and confirms the build is green. ## Quick Start Ask the assistant to fix the failing build or compile error in this project and paste the exact error output or stack trace.

Frequently Asked Questions about build-fix-edho-ferdian

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

FAQPage Schema
How do I fix a build error without breaking other things?

Fix one error at a time with the smallest diff that addresses the root cause, then re-run the actual build command to verify. Never batch unrelated errors into one edit, and treat any new error that surfaces as a fresh diagnosis rather than a continuation of the same fix.

How to diagnose dependency resolution conflicts in Gradle or NuGet?

Run the dependency insight tooling first: ./gradlew :module:dependencyInsight --dependency <name> for Gradle, or dotnet list package --include-transitive for NuGet. These show the actual conflicting version chain so you can align or exclude the right artifact instead of guessing.

Does this build-fix approach support my programming language?

It ships diagnostic references for 17 stacks: JavaScript/TypeScript, Django/Python, Go, Rust, PHP/Laravel, Java/Spring, Kotlin, Swift, React Native, Flutter, Android/KMP, .NET (C# and F#), C++, PyTorch, ArkTS/HarmonyOS, Perl, and Ruby. The stack is auto-detected from lockfiles and config files.

Why is using --fake on a Django migration risky?

--fake marks a migration as applied without running its SQL, so if the database schema does not already match, it leaves the schema silently wrong. Only use it after confirming the schema already reflects what the migration would produce; otherwise it is suppression, not a fix.

When should a build error be escalated instead of fixed?

Escalate when the fix requires an architectural decision: a destructive migration, a module redesign, a dependency major-version bump, or a refactor where the error only goes away by restructuring. Also stop after three failed attempts on the same error rather than continuing to guess.