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

format

Skill439 starsChanged 6 months agoMITView on GitHub

Auto-format code via the developer CLI - backend (.NET via JetBrains cleanupcode), frontend (oxfmt + oxlint --fix), and the developer CLI itself.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 formats everything (changed-only by default).

    line 21
  3. Very specific:

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

    line 23

≈ “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

Format

dotnet run --project developer-cli -- format [--backend] [--frontend] [--cli] [--self-contained-system <name>] [--no-build] [--all-files] --quiet

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

  • --backend - .NET (JetBrains cleanupcode)
  • --frontend - React/TypeScript (oxfmt + oxlint --fix)
  • --cli - the developer CLI itself
  • --self-contained-system <name> - narrows backend formatting to one SCS (e.g. account, main)
  • --no-build - skip the dotnet tool restore step (faster after a recent run)
  • --all-files - format every file in the solution. Default is to format only .cs files changed against origin/main (faster).

No arguments formats everything (changed-only by default). Unformatted code fails CI - commit all changes, never revert.

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

Examples

dotnet run --project developer-cli -- format --quiet                                            # everything
dotnet run --project developer-cli -- format --backend --quiet                                  # all backend
dotnet run --project developer-cli -- format --frontend --quiet                                 # frontend
dotnet run --project developer-cli -- format --backend --self-contained-system account --quiet  # one SCS

Always pass --quiet

Verbose output goes to a log file. On success the CLI prints a single line; on failure it prints a short error message - read the log if you need details. Backend is slow - run last. Frontend is fast.

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