agentleFS
Sign inStart free
finosfinos/git-proxy/.agents/skills/lint/SKILL.md

lint

Skill262 starsChanged 2 months agoApache-2.0View on GitHub

Check and fix code formatting using ESLint and Prettier

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check and fix code formatting using ESLint and Prettier.

    line 6
  2. Distinctive:

    Read AGENTS.md first. It is the canonical project guide for this repository.

    line 8
  3. Very specific:

    Run npm run format:check to see if there are formatting violations

    line 12
  4. Very specific:

    If violations are found, run npm run format to auto-fix them

    line 13
  5. Very specific:

    Run npm run lint to see if there are linting errors

    line 14
  6. Very specific:

    If errors are found, run npm run lint:fix to auto-fix them

    line 15
  7. Distinctive:

    After applying, run git diff --stat to show what files were reformatted

    line 16
  8. Distinctive:

    If no violations are found, say so and stop.

    line 19
  9. Distinctive:

    Do NOT commit the formatting changes — just apply and report.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 66 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

Check and fix code formatting using ESLint and Prettier.

Read AGENTS.md first. It is the canonical project guide for this repository.

Steps:

  1. Run npm run format:check to see if there are formatting violations
  2. If violations are found, run npm run format to auto-fix them
  3. Run npm run lint to see if there are linting errors
  4. If errors are found, run npm run lint:fix to auto-fix them
  5. After applying, run git diff --stat to show what files were reformatted
  6. Summarize the changes (which files, what kind of formatting was fixed)

If no violations are found, say so and stop.

Do NOT commit the formatting changes — just apply and report.

Download now (ZIP)

  • Other versions79 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 79

    1. ray-project/ray★ 44ksame name
    2. FalkorDB/FalkorDB★ 11ksame name
    3. FastLED/FastLED★ 7.5ksame name
    4. fleetdm/fleet★ 7.1ksame name
    5. aaddrick/claude-desktop-debian★ 5.5ksame name
    6. cloudposse/atmos★ 1.4ksame name
    7. ethereum/execution-specs★ 1.2ksame name
    8. adobe/S3Mock★ 1.2ksame name
    9. maxGraph/maxGraph★ 1.2ksame name
    10. jason-effi-lab/karpathy-llm-wiki-vault★ 718same name

    69 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use query, ingest and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • ArtemXTechSkill

      query

      Query data from this vault. USE WHEN user asks about projects, clients, tasks, daily notes. Use grep to extract frontmatter - do NOT read full files.

      Also in 17 projects that use this

    • JaimeGBASkill

      ingest

      Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

      Also in 25 projects that use this

    • PydanticSkill

      coverage

      Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

      Also in 4 projects that use this

    • seongjaeryuSkill

      save

      Complete and save your current thinking to Bindly

      Also in 5 projects that use this

    • BugRogerSkill

      project

      Project lifecycle management. Dispatches to Ada.

      Also in 4 projects that use this

    • AnthropicSkill

      digest

      Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

      Also in 3 projects that use this

  • In this repository10 other files it gives its agents.

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