agentleFS
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/fix-compile-errors/SKILL.md

fix-compile-errors

Skill9 starsChanged 3 months agoMITView on GitHub

Fix compilation/type errors with minimal diff

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Do not commit, push, merge, or run destructive commands without explicit user consent.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Analyze the compilation errors in the current codebase and provide fixes for them, making the necessary changes to resolve all compilation errors.

Steps

  1. Identify compilation errors
    • Type mismatches and casting issues
    • Missing imports or dependencies
    • Syntax errors and malformed code
    • Undefined variables or functions
    • Configuration issues
  2. Fix each error
    • Identify the root cause
    • Provide the corrected code
    • Explain why the fix resolves the issue

Fix Compile Errors Checklist

  • Identified all type mismatches and casting issues
  • Fixed missing imports or dependencies
  • Corrected syntax errors and malformed code
  • Fixed undefined variables or functions
  • Resolved configuration issues
  • Provided corrected code for each error
  • Explained why each fix resolves the issue
  • Verified all compilation errors are resolved

Guardrails

  • Resolve the real type or compile error with the smallest correct change; do not disable checks or loosen types to force a green build.
  • Make a minimal diff; do not refactor unrelated code while fixing compile errors.
  • Do not commit, push, merge, or run destructive commands without explicit user consent.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.