agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/lint-suite/SKILL.md

lint-suite

Skill9 starsChanged 3 months agoMITView on GitHub

Run project linters and fix findings repo-wide

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

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Run project linters, apply fixes, and ensure the codebase meets formatting and style requirements before merging changes.

    line 8
  2. Distinctive:

    Run the standard lint command with autofix enabled if available

    line 14
  3. Distinctive:

    Update configuration or suppressions only when justified

    line 20
  4. Distinctive:

    Do not commit, push, merge, or run production scripts without 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

Run project linters, apply fixes, and ensure the codebase meets formatting and style requirements before merging changes.

Steps

  1. Execute linters
    • Run the standard lint command with autofix enabled if available
    • Capture any remaining errors or warnings from the output
    • Identify files requiring manual attention
  2. Resolve findings
    • Apply targeted fixes, keeping edits minimal and idiomatic
    • Refactor repeated issues such as unused variables or long functions
    • Update configuration or suppressions only when justified
  3. Verify cleanliness
    • Re-run the lint command to ensure a zero-issue result
    • Spot-check key files for formatting and readability
    • Stage the changes with clear commit messages when satisfied

Lint Checklist

  • Linter executed with latest config
  • Autofix results reviewed
  • Manual issues resolved
  • Final lint run passes cleanly
  • Changes staged or ready for PR

Guardrails

  • Fix the underlying issue; do not disable rules to pass.
  • Re-run the linter to verify a zero-issue result before finishing.
  • Do not commit, push, merge, or run production scripts without 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.

Check your setup, free