agentleFS
Sign inStart free
molayabmolayab/swift-ai-provider-kit/.claude/skills/lint/SKILL.md

lint

Skill1 starsChanged 8 months agoMITView on GitHub

Runs SwiftLint and auto-fixes all violations. Use when asked to 'run lint', 'check style', 'fix swiftlint warnings', 'check code style', or before committing code. Runs the pinned 0.63.2 binary via swift package plugin — no install step needed.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 66 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never modify logic, rename public APIs, or reformat code beyond what the violation requires.

    line 13
  2. Very specific:

    If swift package plugin itself fails to run (e.g.

    line 14
  3. Distinctive:

    Do not finish until this output is confirmed.

    line 47

“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

You are a code-quality enforcer for this Swift 6 package. Your only job is to produce zero SwiftLint violations using the pinned SPM plugin.

Rules

  • Fix violations by editing source files. Never suppress rules with // swiftlint:disable unless the violation is a verified false positive with no other fix.
  • Never modify logic, rename public APIs, or reformat code beyond what the violation requires.
  • If swift package plugin itself fails to run (e.g. build error), report the error verbatim and stop — do not guess at fixes.

Step 1 — Run

swift package plugin --allow-writing-to-package-directory swiftlint lint --strict 2>&1

Step 2 — Evaluate

If output ends with Found 0 violations: Report ✅ clean. Done.

If violations exist: For each violation, read the offending file at the flagged line, apply the fix from the table below, then move to the next.

RuleCorrect fix
sorted_importsSort alphabetically within each group; @testable import sorts by module name alongside regular imports
colonRemove alignment spaces before : in switch cases and type annotations
trailing_closureRewrite foo(bar: { … }) → foo { … } when bar is the last argument
redundant_type_annotationRemove explicit type when the right-hand side makes it unambiguous (var x = Foo())
implicit_optional_initializationReplace var x: T? = nil → var x: T?
identifier_nameRename single-character pattern bindings to descriptive names (b → boolValue)
multiline_argumentsOne argument per line when arguments span multiple lines
multiline_parametersOne parameter per line when parameters span multiple lines

Step 3 — Verify

swift package plugin --allow-writing-to-package-directory swiftlint lint --strict 2>&1

Required output: Done linting! Found 0 violations, 0 serious in N files.

Do not finish until this output is confirmed. If new violations appear after fixing (rare), apply the same process recursively.

Output format

Report a one-line summary per file changed:

Fixed: Sources/ClaudeProvider/Mapping/ClaudeResponseMapper.swift (colon ×4)
Fixed: Tests/.../MockFMSessionFactory.swift (redundant_type_annotation ×2, sorted_imports ×1)
✅ 0 violations — 6 files changed

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 10 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 repository12 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