check-compiler-errors

Runs compile and type-check commands and summarizes failures by file and category.

3|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill check-compiler-errors-zanzythebar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-compiler-errors
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/check-compiler-errors
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill check-compiler-errors-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Compile and type-check failures often block local validation and CI pipelines, and manually hunting down the right commands and parsing raw error output wastes time. This Skill discovers the correct commands, runs them, and organizes errors into an actionable summary. ## Core Features & Use Cases - Command Discovery: Locates compile and type-check commands from package scripts, task files, CI configuration, or project documentation. - Structured Error Reporting: Groups errors by file and category so the most impactful issues are visible first. - Iterative Fixing: Applies highest-confidence fixes first and re-runs checks until the build is clean or blockers remain. - Use Case: A TypeScript project's CI fails on type errors. Use this Skill to find the type-check script, run it, get a grouped error summary, and fix the issues one by one until the check passes. ## Quick Start Ask the assistant to run the project's compile and type-check commands, summarize any errors by file, and fix them until the checks pass.

Frequently Asked Questions about check-compiler-errors

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

FAQPage Schema
How do I find and fix type-check errors in my project?

The Skill discovers type-check commands from package scripts, task files, or CI config, runs the narrowest relevant command first, then groups errors by file and category. It fixes the highest-confidence issues first and re-runs until checks pass.

How to diagnose compile failures blocking CI pipelines?

Run the compile command identified from your CI configuration or project docs, then review the error summary grouped by file and type. Fix issues iteratively, starting with the highest-confidence ones, and re-run the check after each fix.

Does this work with any programming language or build tool?

Yes, it works with any project that defines compile or type-check commands in package scripts, task files, CI config, or documentation. It discovers the commands rather than relying on a specific toolchain.

What happens if errors remain after automatic fixes?

The Skill reports remaining blockers after applying the highest-confidence fixes. It re-runs checks until the build is clean or it is blocked, then summarizes what was fixed and what still needs manual attention.

When should I not rely on automated compile error fixing?

Avoid automated fixes when errors stem from ambiguous design decisions, large refactors, or unclear intended behavior. In those cases the grouped error summary is still useful, but fixes should be reviewed and applied manually.