agentleFS
Sign inStart free
platformplatformplatformplatform/PlatformPlatform/.claude/skills/lint/SKILL.md

lint

Skill439 starsChanged 6 months agoMITView on GitHub

Lint code via the developer CLI - backend (.NET via JetBrains inspectcode), frontend (oxlint), and the developer CLI itself.

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects 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 26 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 67 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use developer-cli exactly as written - do not expand to an absolute worktree path.

    line 12
  2. Distinctive:

    No arguments lints the whole solution.

    line 21
  3. Very specific:

    After build succeeds, run format, lint, test in parallel with --no-build.

    line 23
  4. Very specific:

    Routine work: use --changed-only. Most lint findings are local (style, naming, hints) and the saving is large (~4m → ~30s).

    line 29

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

dotnet run --project developer-cli -- lint [--backend] [--frontend] [--cli] [--self-contained-system <name>] [--no-build] [--changed-only] --quiet

Use developer-cli exactly as written - do not expand to an absolute worktree path.

  • --backend - .NET (JetBrains inspectcode)
  • --frontend - React/TypeScript (oxlint)
  • --cli - the developer CLI itself
  • --self-contained-system <name> - narrows backend linting to one SCS (e.g. account, main)
  • --no-build - skip the rebuild step (faster after a recent build)
  • --changed-only - lint only .cs files changed against origin/main (much faster; see guidance below)

No arguments lints the whole solution. Every finding fails CI regardless of severity - fix all of them.

After build succeeds, run format, lint, test in parallel with --no-build. Backend lint is slow - run last. Frontend lint often needs code rewrites - run after each bigger change.

When to use --changed-only

Inspectcode has cross-file rules ("unused public method", "member can be private", flow analysis across method calls). --changed-only only inspects the listed files - it doesn't catch issues in untouched files that became invalid because of edits elsewhere.

  • Routine work: use --changed-only. Most lint findings are local (style, naming, hints) and the saving is large (~4m → ~30s).
  • Larger changes that affect other files (refactoring a public API, deleting a method's only caller, changing a widely-used type): omit --changed-only and lint the full solution.

CI always lints the full solution, so anything missed by a local --changed-only run gets caught before merge.

Examples

dotnet run --project developer-cli -- lint --quiet                                                # everything (full solution)
dotnet run --project developer-cli -- lint --backend --changed-only --quiet                       # backend, changed files only (recommended for routine work)
dotnet run --project developer-cli -- lint --frontend --quiet                                     # frontend
dotnet run --project developer-cli -- lint --backend --self-contained-system main --quiet         # one SCS, full

Always pass --quiet

Verbose output goes to a log file. On success the CLI prints a single line; on failure it prints where to find the findings and exits 1.

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