New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Format

by managedcode in managedcode/dotnet-skills

Format or verify trusted .NET projects with the SDK-provided dotnet format command.

MITAuto-check passedDevelopment

Install Format

skills CLI
$ npx skills add managedcode/dotnet-skills --skill format -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills format --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Format/skills/format .claude/skills/format && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
format
GitHub stars
486
Token cost
~893 tokens
SKILL.md length
412 words
Files
4 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Format or verify trusted .NET projects with the SDK-provided dotnet format command.

  • Works in 8 steps: Read the nearest AGENTS.md, global.json,… → Confirm the exact trusted workspace to… → Determine whether the request is… → …
  • Checking .editorconfig-driven whitespace
  • SKILL.md covers Diagnostic Output Budget, Workflow, Invariants and References
  • Calls dotnet and git

What it does

Format is an agent skill from managedcode/dotnet-skills. Format or verify trusted .NET projects with the SDK-provided dotnet format command. USE FOR: applying or checking .editorconfig-driven whitespace, code-style, or analyzer fixes; adding a --verify-no-changes CI gate; diagnosing formatter scope or load failures. DO NOT USE FOR: repositories where another formatter exclusively owns the affected files; analyzer policy with no formatter work; mutating files when the user requested only diagnosis.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `manifest.json`, `references/commands.md` and `references/config.md`).

It sits in Development, covering Linting and formatting. It works with .NET. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • Checking .editorconfig-driven whitespace
  • Adding a --verify-no-changes CI gate
  • Diagnosing formatter scope
  • : repositories where another formatter exclusively owns the affected files

Example prompts

  • “/format”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the nearest AGENTS.md, global.json, solution/project files, .editorconfig, and current Git status.
  2. Confirm the exact trusted workspace to load. dotnet format may restore, compile, and run analyzers from that workspace.
  3. Determine whether the request is read-only verification or permission to apply fixes. Do not run a mutating command for a review…
  4. Preserve the current diff before formatting. When scope is uncertain, begin with --verify-no-changes or a narrow --include list.
  5. Choose the smallest formatter surface that matches the request
  6. Treat --include and --exclude values as workspace-relative file or directory paths, not shell globs. Use --diagnostics to narrow style or…
  7. After a mutating run, inspect git diff --stat, representative diffs, line endings, and every changed file. If scope is unexpectedly broad…
  8. Rerun the matching command with --verify-no-changes. When analyzer fixes were applied, also build and run the tests relevant to the…

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Format loads about 893 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 412 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~893
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 412 words, ~893 tokens.

Download SKILL.mdSave it as .claude/skills/format/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
format
description
Format or verify trusted .NET projects with the SDK-provided `dotnet format` command. USE FOR: applying or checking `.editorconfig`-driven whitespace, code-style, or analyzer fixes; adding a `--verify-no-changes` CI gate; diagnosing formatter scope or load failures. DO NOT USE FOR: repositories where another formatter exclusively owns the affected files; analyzer policy with no formatter work; mutating files when the user requested only diagnosis.

dotnet format

Use the formatter already shipped with the selected .NET SDK. Preserve the repository's formatter ownership, existing changes, and configured style instead of introducing new preferences.

Diagnostic Output Budget

Keep warnings/errors and a concise result; avoid routine verbose or diagnostic console output. Preserve native progress/ANSI when running tests. On failure, show only the relevant diagnostic and stack frames, deduplicated and capped at 80 lines / 8 KiB per response. Collect extra diagnostics only for an unresolved problem in size-bounded artifacts outside model context; link them and inspect exact bounded excerpts. Never dump full logs/reports or hide the command exit code through filtering.

Workflow

  1. Read the nearest AGENTS.md, global.json, solution/project files, .editorconfig, and current Git status.
  2. Confirm the exact trusted workspace to load. dotnet format may restore, compile, and run analyzers from that workspace.
  3. Determine whether the request is read-only verification or permission to apply fixes. Do not run a mutating command for a review, explanation, or diagnosis request.
  4. Preserve the current diff before formatting. When scope is uncertain, begin with --verify-no-changes or a narrow --include list.
  5. Choose the smallest formatter surface that matches the request:
    • whitespace for indentation, spacing, and line-ending rules;
    • style for built-in .NET code-style diagnostics;
    • analyzers for fixable non-style analyzer diagnostics;
    • the command without a subcommand only when all applicable surfaces are intended.
  6. Treat --include and --exclude values as workspace-relative file or directory paths, not shell globs. Use --diagnostics to narrow style or analyzer fixes by rule ID.
  7. After a mutating run, inspect git diff --stat, representative diffs, line endings, and every changed file. If scope is unexpectedly broad, stop and narrow the command; never discard pre-existing user changes.
  8. Rerun the matching command with --verify-no-changes. When analyzer fixes were applied, also build and run the tests relevant to the changed behavior.
Show full SKILL.md (110 more words)Show less

Invariants

  • .editorconfig and existing MSBuild analyzer configuration are the source of truth. Do not add an arbitrary style template unless the user asks for one.
  • Use --no-restore only after dependencies have already been restored successfully.
  • Generated files stay excluded unless the repository explicitly owns and formats them.
  • A successful formatter process does not prove that every diagnostic has an automatic fix. Review its output or JSON report and use build/analyzer results as the final evidence.
  • Keep formatter responsibilities explicit when CSharpier, ReSharper cleanup, generated-code tools, or other formatters coexist.

References

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in catalog/Tools/Format/skills/format of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/commands.md
  • references/config.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Format next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Format compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Format this skillmanagedcode/dotnet-skills486—~893Automated safety check: PassMIT
Setup Husky DotnetSebastienDegodez/copilot-instructions197—~1.3kAutomated safety check: PassApache-2.0
Git HooksProrise-cool/Claude-Code-Multi-Agent305—~3.6kAutomated safety check: NotesNone
Lintplatformplatform/PlatformPlatform440—~632Automated safety check: PassMIT
Precheckayutaz/piper-plus218—~647Automated safety check: PassMIT
Code Completionfacioquo/stock-indicators-dotnet1.2k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Setup Husky Dotnet

    SebastienDegodez/copilot-instructions

    A skill your agent uses when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically

    197 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Git Hooks

    Prorise-cool/Claude-Code-Multi-Agent

    Central authority on git hook implementations, modern best practices, and tooling for .NET/C, JavaScript/TypeScript, Python, and polyglot repositories.

    305 GitHub stars~3.6k tokensUpdated 21 days ago
    DevelopmentAuto-check: notes

  • Lint

    platformplatform/PlatformPlatform

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

    440 GitHub stars~632 tokensUpdated 13 days ago
    DevelopmentAuto-check passed

  • Precheck

    ayutaz/piper-plus

    PR 作成前の lint + format + test 一括実行。引数で scope (python/rust/cs/go/js/cpp/all) を指定可能。未指定なら git diff から自動判定。

    218 GitHub stars~647 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Completion

    facioquo/stock-indicators-dotnet

    Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Mcaf Dotnet Csharpier

    managedcode/Storage

    Use the open-source free CSharpier formatter for C and XML. An agent skill from managedcode/Storage.

    138 GitHub stars~961 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Format

What does Format do?

Format or verify trusted .NET projects with the SDK-provided dotnet format command. Format is an agent skill from managedcode/dotnet-skills.NET projects with the SDK-provided dotnet format command.

When should I use Format?

Format fits situations like: checking .editorconfig-driven whitespace; adding a --verify-no-changes CI gate; diagnosing formatter scope; : repositories where another formatter exclusively owns the affected files.

How do I install Format in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill format -a claude-code`. Or copy the skill folder (catalog/Tools/Format/skills/format in managedcode/dotnet-skills) into .claude/skills/format in your project. Claude Code loads it when a task matches its description.

How do I install Format in Codex?

Run `npx skills add managedcode/dotnet-skills --skill format -a codex`. Or copy the skill folder (catalog/Tools/Format/skills/format in managedcode/dotnet-skills) into .agents/skills/format in your project. Codex loads it when a task matches its description.

Can I use Format in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill format -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/format, .gemini/skills/format, .github/skills/format and .opencode/skills/format in your project.

What does Format need to run?

Going by SKILL.md and its folder, Format needs the command-line tools its instructions call (dotnet and git).

Does Format access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Format safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Format use?

Format is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Format use?

About 893 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Format?

Skills that share tags, products or a category with Format: Setup Husky Dotnet (SebastienDegodez/copilot-instructions, 197 stars), Git Hooks (Prorise-cool/Claude-Code-Multi-Agent, 305 stars), Lint (platformplatform/PlatformPlatform, 440 stars) and Precheck (ayutaz/piper-plus, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Format?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.