agentleFS
gologo13gologo13/agent-skills/skills/lint-fix/SKILL.md

lint-fix

Skill0 starsChanged 9 months agoMITView on GitHub

Analyze the current file for linting issues and automatically fix them according to the proj...; keywords: lint, fix. Use only on explicit request; skip in routine implementation discussions.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Distinctive:

    Remove unused imports and variables

    line 22
  2. Distinctive:

    Add missing semicolons or correct indentation

    line 23

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “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

Lint and Fix Code

Overview

Analyze the current file for linting issues and automatically fix them according to the project's coding standards, then apply the fixes directly to the code and explain what changes were made.

Steps

  1. Identify linting issues
    • Code formatting and style consistency
    • Unused imports and variables
    • Missing semicolons or proper indentation
    • Best practice violations
    • Type safety issues
  2. Apply fixes
    • Fix formatting and style issues
    • Remove unused imports and variables
    • Add missing semicolons or correct indentation
    • Apply best practice corrections
    • Fix type safety issues
    • Explain what changes were made

Lint and Fix Code Checklist

  • Identified all code formatting and style issues
  • Identified unused imports and variables
  • Identified missing semicolons or indentation issues
  • Identified best practice violations
  • Identified type safety issues
  • Applied all formatting and style fixes
  • Removed unused imports and variables
  • Fixed indentation and added missing semicolons
  • Applied best practice corrections
  • Fixed type safety issues
  • Explained what changes were made

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.