القائمة
Use when you need to find unused methods in a C# solution, trace who calls a method, assess removal impact before refactoring, or generate call-graph documentation/diagrams for C# code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Anthropic API rate limit handling - retry logic, backoff, throttling for batch workloads against Claude models
Use when building an automated test → issue → fix loop with Claude Code and GitHub issues — overnight auto-fixing, regression loops, self-healing CI.
Use when creating, editing, publishing, or deleting posts on Cyril's Workshop blog or the steponnopets.net devblog.
Use when writing or contributing a boofuzz network-protocol fuzzer in this repo — layout, formatting rules, and reading results.
Use when a task needs real-time control of a connected browser via the Browser Bridge Broker — submit JS jobs over HTTP that browsers eval and return.
Use when training a character LoRA (Chroma/Flux or Pony/SDXL) on a RunPod GPU and wiring it into the ComfyUI + pony_web render stack.
| name | CSharpener |
| description | Use when you need to find unused methods in a C# solution, trace who calls a method, assess removal impact before refactoring, or generate call-graph documentation/diagrams for C# code. |
Roslyn-based static analysis for C# solutions: call graphs, unused-code detection, impact analysis, HTML docs, Graphviz export.
Primary: Y:/CSharpDLLs/CSharpener/CSharpener.exe — use forward slashes for the exe path in bash; the --solution argument takes a normal Windows path. Don't search for the executable, use this path directly.
Fallback if Y: is unavailable — build from https://github.com/lawless-m/CSharpener with dotnet build -c Release; output is CSharpCallGraphAnalyzer\bin\Release\net9.0\win-x64\csharp-analyzer.exe.
"Y:/CSharpDLLs/CSharpener/CSharpener.exe" <command> --solution "<path>" --format console
| Command | Purpose | Extra options |
|---|---|---|
analyze | Full analysis: call graph, unused methods, stats | --include-call-graph (default true), --exclude-namespace |
unused | Find unused methods with confidence levels | --exclude-namespace |
callers | Who calls a method | --method, -m (partial name OK, case-insensitive) |
dependencies | What a method calls | --method, -m |
impact | What breaks if a method is removed (direct/transitive callers, affected entry points) | --method, -m |
document | HTML docs with cross-referenced code and call graphs | --output, -o (required), --include-unused, --include-tests |
Common options: --solution, -s (required, .sln or .csproj, absolute path), --format, -f (json default; console, dot/graphviz, html), --output, -o.
unused)| Level | Meaning |
|---|---|
| High | Private methods never called — safe to remove |
| Medium | Internal methods not called within assembly — review |
| Low | Public methods — might be external API, caution |
.csharpener-cache/ in the solution directory. First run is slow; subsequent runs fast. Delete the cache to force a refresh; it invalidates on file changes.--exclude-namespace "*.Tests,*.Test" or analyze individual projects.dotnet build first — the solution may not compile.