메뉴
Run C# static analysis, auto-fix code issues, format code, find unused code, and enforce coding standards in .NET projects. Use when the user asks about code quality, linting, static analysis, code cleanup, unused code, or formatting in C# / .NET projects.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/asynkron/asynkron-skills --skill roslynator명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Evaluate and improve an API by inventing real, valuable tasks, attempting them through the public API, measuring the usefulness of its features and data, and turning failures into verified fixes or evidence-backed retirement proposals. Use when asked to dogfood, audit, rationalize, improve, simplify, or find value in an API; assess whether endpoints or features produce useful information; or decide what to keep, fix, combine, document, or retire.
Keep iterating on the next logical step in a project until a clear stop condition is reached. Use when the user says `/continue-loop`, asks to "keep going", "continue iterating", or wants Codex to repeatedly choose the highest-leverage next task, execute it, verify it, and then continue. Good for open-ended cleanup, refactoring, polish, debt burn-down, and project advancement where the next step should be discovered from the current repo state instead of handed over explicitly.
Find and explain churn hotspots and unstable code clusters in a git repo. Goes beyond a flat "most-edited files" list — auto-detects clusters by directory, by filename stem (foo.go + foo_test.go), and by co-change (files that change together) — then classifies each cluster (unstable / under-development / buggy / tightly-coupled / spec-shifting) and explains *why* it's a problem. Trigger whenever the user asks about churn, hotspots, unstable code, files that change a lot, refactoring candidates, technical debt hotspots, "what's a mess", "/hotmess", or any combination of folder + time window where they want insight rather than just numbers. Auto-detects code files when no extension is given.
| name | roslynator |
| description | Run C# static analysis, auto-fix code issues, format code, find unused code, and enforce coding standards in .NET projects. Use when the user asks about code quality, linting, static analysis, code cleanup, unused code, or formatting in C# / .NET projects. |
| argument-hint | [solution or project path] |
Check if roslynator is installed:
which roslynator
If not found, try running via dnx (no install needed, .NET 10+):
dnx Roslynator.DotNet.Cli [command] [options]
Or install globally:
dotnet tool install -g roslynator.dotnet.cli
Roslynator is a set of code analysis tools for C# powered by Roslyn. It provides 500+ analyzers, refactorings, and code fixes. The CLI tool can analyze, fix, and format entire solutions from the command line — no IDE needed.
The CLI itself contains no analyzers — they come from NuGet packages referenced in your project (e.g. Roslynator.Analyzers) or via --analyzer-assemblies.
Fix all diagnostics in a solution:
roslynator fix MySolution.sln
Fix all diagnostics in a project:
roslynator fix MyProject.csproj
Analyze without fixing (report only):
roslynator analyze MySolution.sln
Format code:
roslynator format MySolution.sln
Find unused code (dead code detection):
roslynator find-unused MySolution.sln
List symbols:
roslynator list-symbols MySolution.sln
Count lines of code:
roslynator lloc MySolution.sln
| Command | Purpose |
|---|---|
fix | Auto-fix diagnostics in project/solution |
analyze | Report diagnostics without fixing |
format | Format whitespace |
find-unused | Find unused declarations (dead code) |
list-symbols | List types, members, and symbols |
lloc | Count logical lines of code |
loc | Count physical lines of code |
spellcheck | Check spelling in comments and strings |
| Flag | Purpose |
|---|---|
--projects <name> | Only process named projects |
--ignored-projects <name> | Skip specific projects |
--include <glob> | Include matching files/folders |
--exclude <glob> | Exclude matching files/folders |
-v, --verbosity <level> | Output level: quiet, minimal, normal, detailed, diagnostic |
-p, --properties <NAME=VALUE> | MSBuild properties (e.g. Configuration=Release) |
-m, --msbuild-path <dir> | Path to MSBuild directory |
--language <lang> | Language: cs or vb |
-g, --include-generated-code | Include generated code |
--file-log <path> | Write output to file |
-h, --help | Show help |
| Flag | Purpose |
|---|---|
-a, --analyzer-assemblies <path> | Paths to additional analyzer assemblies |
--supported-diagnostics <id> | Report only these diagnostic IDs |
--ignored-diagnostics <id> | Skip these diagnostic IDs |
--severity-level <level> | Minimum severity: hidden, info, warning, error |
--ignore-compiler-diagnostics | Hide compiler messages |
-o, --output <path> | Save diagnostics to file |
--output-format | Report format: xml or gitlab |
--execution-time | Measure analyzer performance |
Roslynator is configured via .editorconfig in your project:
Set severity for all Roslynator analyzers:
[*.cs]
dotnet_analyzer_diagnostic.category-roslynator.severity = warning
Enable/disable specific analyzers:
[*.cs]
dotnet_diagnostic.RCS1001.severity = none # Disable specific rule
dotnet_diagnostic.RCS1036.severity = error # Upgrade to error
Enable/disable refactorings:
[*.cs]
roslynator_refactoring.add_braces.enabled = false
| Code | Meaning |
|---|---|
0 | Success — no diagnostics found or all fixed |
1 | Diagnostics found or not all fixed |
2 | Error or execution canceled |
Roslynator is used in the /pre-pr quality gate as the first step:
roslynator fix — auto-fix code issuesdotnet build — verify compilationdotnet test — run testsquickdup — check for duplicationdotnet format — format coderoslynator analyze — it needs compiled outputroslynator fix for auto-fixing, roslynator analyze for CI reporting--severity-level warning to skip info/hidden diagnostics in CI--ignored-diagnostics to suppress known false positivesroslynator find-unused periodically to catch dead code.editorconfig rather than via CLI flags for consistency across teamSOC 직업 분류 기준
