Speckit Constitution
WeihanLi/WeihanLi.Common
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
A skill your agent uses when adding a Roslynator code fix for C compiler error CS or RCF, editing Diagnostics.xml or CodeFixes.xml, or when compiler-diagnostic-fixes-testing.md shows…
Install Add Compiler Diagnostic Fix
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fix --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .claude/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.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/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .claude/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fixType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .agents/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .agents/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .cursor/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .cursor/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dotnet/roslynator.git --path .claude/skills/add-compiler-diagnostic-fix--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .gemini/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .gemini/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fixInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .github/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .github/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dotnet/roslynator add-compiler-diagnostic-fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dotnet/roslynator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/add-compiler-diagnostic-fix .opencode/skills/add-compiler-diagnostic-fix && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-compiler-diagnostic-fix" agent skill from https://github.com/dotnet/roslynator/tree/main/.claude/skills/add-compiler-diagnostic-fix into .opencode/skills/add-compiler-diagnostic-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-compiler-diagnostic-fix", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-compiler-diagnostic-fix- GitHub stars
- 3.5k
- Token cost
- ~1k tokens
- SKILL.md length
- 331 words
- Files
- 2 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when adding a Roslynator code fix for C compiler error CS or RCF, editing Diagnostics.xml or CodeFixes.xml, or when compiler-diagnostic-fixes-testing.md shows…
- Works in 2 steps: Confirm metadata parameters (hard gate… → Full XML, provider, and test patterns:…
- Adding a Roslynator code fix for C compiler error CS
- SKILL.md covers Overview, When to Use, Confirm metadata parameters… and Quick Reference, plus 2 more sections
- Calls pwsh and dotnet
What it does
Add Compiler Diagnostic Fix is an agent skill from dotnet/roslynator, published by the product's own GitHub organization. Use when adding a Roslynator code fix for C compiler error CS or RCF, editing Diagnostics.xml or CodeFixes.xml, or when compiler-diagnostic-fixes-testing.md shows XunitCompilerDiagnosticFixVerifier or bare DiagnosticId like "CS0106" — in-repo uses AbstractCSharpCompilerDiagnosticFixVerifier and CompilerDiagnosticIdentifiers. Contributor how-to exists but testing page targets NuGet consumers.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation.md`).
It sits in Development. It works with C# and .NET. The repository describes itself as: Roslynator is a set of code analysis tools for C, powered by Roslyn.
When your agent uses it
- Adding a Roslynator code fix for C compiler error CS
- Editing Diagnostics.xml
- Compiler-diagnostic-fixes-testing.md shows XunitCompilerDiagnosticFixVerifier
- Bare DiagnosticId like CS0106 — in-repo uses AbstractCSharpCompilerDiagnosticFixVerifier and CompilerDiagnosticIdentifiers
Example prompts
- “CS0106”
- “/add-compiler-diagnostic-fix”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Confirm metadata parameters (hard gate above).
- Full XML, provider, and test patterns: references/implementation.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 167f434. 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:
pwshdotnet
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
josefpihrt.github.io
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
Add Compiler Diagnostic Fix loads about 1k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 331 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 331 words (~1,033 tokens).
“Compiler fixes use Diagnostics.xml + CodeFixes.xml → codegen → CompilerDiagnosticCodeFixProvider → test. Contributor how-to: how-to-add-compiler-diagnostic-fix. Do not follow compiler-diagnostic-fixes-testing alone — it targets NuGet consumers.”
- name
- add-compiler-diagnostic-fix
Files
SKILL.md and 1 other file (references) in .claude/skills/add-compiler-diagnostic-fix of dotnet/roslynator.
- SKILL.md
- references/implementation.md
Open the folder on GitHubat commit 167f434
Compare with similar skills
Add Compiler Diagnostic Fix 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Compiler Diagnostic Fix this skilldotnet/roslynator | 3.5k | — | ~1k | Automated safety check: Pass | Custom licence | |
| Speckit ConstitutionWeihanLi/WeihanLi.Common | 242 | 11 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Analyzing .NET Performancedotnet/skills | 5.6k | 3 repos | ~3.1k | Automated safety check: Pass | MIT | |
| GitVersion .NET DevelopmentGitTools/GitVersion | 3.1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Code Reviewdotnet/macios | 2.9k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Code Reviewjonathanpeppers/dotnes | 780 | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Analyzing .NET Performance
dotnet/skills
Scans C# and .NET code for about 50 performance anti-patterns and reports prioritized findings with concrete fixes, at a scan depth you choose.
GitVersion .NET Development
GitTools/GitVersion
Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.
- Official
Code Review
dotnet/macios
Review dotnet/macios PRs against established rules. An agent skill from dotnet/macios.
Code Review
jonathanpeppers/dotnes
Review dotnes pull requests against established repository rules.
Dynamo Dotnet Expert
DynamoDS/Dynamo
Write and review C/.NET code in Dynamo following Dynamo coding standards, modern C patterns, and repo conventions.
More from dotnet/roslynator
- Official
Add Analyzer
dotnet/roslynator
A skill your agent uses when adding a new RCS diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator EditorConfig options, or when docs say CHANGELOG.md…
- Official
Add Refactoring
dotnet/roslynator
A skill your agent uses when adding a new RR refactoring in roslynator, editing Refactorings.xml, registering in RefactoringContext, or when refactorings-testing.md shows XunitRefactoringVerifier —…
- Official
Fix Analyzer Bug
dotnet/roslynator
A skill your agent uses when fixing a Roslynator analyzer false positive or false negative, RCS, RR, or CS/RCF regression, incorrect diagnostic reporting, or bug report citing a specific rule id —…
- Official
Release Roslynator
dotnet/roslynator
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
- Official
Deprecate Analyzer Or Refactoring
dotnet/roslynator
A skill your agent uses when obsoleting or retiring RCS, RR, or RCF in roslynator, replacing an analyzer with another id, or when tempted to use IsObsolete on an Analyzer entry — analyzers use…
Related
Categories
Questions about Add Compiler Diagnostic Fix
What does Add Compiler Diagnostic Fix do?
A skill your agent uses when adding a Roslynator code fix for C compiler error CS or RCF, editing Diagnostics.xml or CodeFixes.xml, or when compiler-diagnostic-fixes-testing.md shows…. Add Compiler Diagnostic Fix is an agent skill from dotnet/roslynator, published by the product's own GitHub organization.md shows XunitCompilerDiagnosticFixVerifier or bare DiagnosticId like "CS0106" — in-repo uses AbstractCSharpCompilerDiagnosticFixVerifier and CompilerDiagnosticIdentifiers.
When should I use Add Compiler Diagnostic Fix?
Add Compiler Diagnostic Fix fits situations like: adding a Roslynator code fix for C compiler error CS; editing Diagnostics.xml; compiler-diagnostic-fixes-testing.md shows XunitCompilerDiagnosticFixVerifier; bare DiagnosticId like CS0106 — in-repo uses AbstractCSharpCompilerDiagnosticFixVerifier and CompilerDiagnosticIdentifiers.
How do I install Add Compiler Diagnostic Fix in Claude Code?
Run `npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a claude-code`. Or copy the skill folder (.claude/skills/add-compiler-diagnostic-fix in dotnet/roslynator) into .claude/skills/add-compiler-diagnostic-fix in your project. Claude Code loads it when a task matches its description.
How do I install Add Compiler Diagnostic Fix in Codex?
Run `npx skills add dotnet/roslynator --skill add-compiler-diagnostic-fix -a codex`. Or copy the skill folder (.claude/skills/add-compiler-diagnostic-fix in dotnet/roslynator) into .agents/skills/add-compiler-diagnostic-fix in your project. Codex loads it when a task matches its description.
Can I use Add Compiler Diagnostic Fix 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 dotnet/roslynator --skill add-compiler-diagnostic-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-compiler-diagnostic-fix, .gemini/skills/add-compiler-diagnostic-fix, .github/skills/add-compiler-diagnostic-fix and .opencode/skills/add-compiler-diagnostic-fix in your project.
What does Add Compiler Diagnostic Fix need to run?
Going by SKILL.md and its folder, Add Compiler Diagnostic Fix needs the command-line tools its instructions call (pwsh and dotnet).
Does Add Compiler Diagnostic Fix access the network?
SKILL.md names 1 domain. As links in the text: josefpihrt.github.io. This is read from the text; nothing was executed.
Is Add Compiler Diagnostic Fix 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 Add Compiler Diagnostic Fix use?
Add Compiler Diagnostic Fix has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Add Compiler Diagnostic Fix use?
About 1k tokens (SKILL.md is roughly 4.1k 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 837 tokens, read only when the agent opens those files.
What are the alternatives to Add Compiler Diagnostic Fix?
Skills that share tags, products or a category with Add Compiler Diagnostic Fix: Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Analyzing .NET Performance (dotnet/skills, 5.6k stars), GitVersion .NET Development (GitTools/GitVersion, 3.1k stars) and Code Review (dotnet/macios, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Compiler Diagnostic Fix?
dotnet (a GitHub organization, an official publisher) maintains it in dotnet/roslynator, which has 3,485 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 4, 2026.
Source: dotnet/roslynator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.