Instructions file CodexOpenCode
AGENTS.md instructions for darylmcd/Roslyn-Backed-MCP, covering agents bootstrap, file purpose (critical), standing engineering directives, canonical rule sources and session start (required).
Instructions file CodexOpenCode
AGENTS.md instructions for darylmcd/Roslyn-Backed-MCP, covering agents bootstrap, file purpose (critical), standing engineering directives, canonical rule sources and session start (required).
Instructions file
Claude Code instructions for darylmcd/Roslyn-Backed-MCP: This project's agent guidelines live in AGENTS.md — read that file now.
Agent
Run one context-heavy /mcp-server-stress phase and return a compact structured summary to the orchestrator. Use for Phase 1 diagnostics, Phase 2 metrics, Phase 3 deep symbol analysis, Phase 4 flow analysis, Phase 8 build/test validation, and Phase 8b concurrency stress. Never run Phase 6 refactoring or any…
Skill Claude CodeCodex
Solution health check. Use when: analyzing a C# solution or project, checking build health, finding diagnostics, assessing code quality, or getting an overview of a .sln/.csproj. Takes a path to a solution or project file as input.
Skill Claude CodeCodex
Layering and Dependency-Inversion-Principle audit of a C# solution. Use when: auditing layering, detecting cycles, checking DIP compliance, or finding cross-layer leaks. Takes an optional project or namespace filter as input.
Skill Claude CodeCodex
Roslyn code actions (fixes and refactorings). Use when: applying IDE-style quick fixes or refactorings at a position or selection, including introduce parameter and inline temporary variable. Takes file path and line/column (and optional selection end) as input.
Skill Claude CodeCodex
Complexity hotspot analysis. Use when: finding complex methods, identifying god classes, measuring maintainability, or planning refactoring priorities in a C# solution. Optionally takes a project name.
Skill Claude CodeCodex
Dead code detection and cleanup. Use when: finding unused symbols, removing dead code, cleaning up unreferenced private/internal members, or auditing a C# project for code that can be safely deleted. Optionally takes a project name.
Skill Claude CodeCodex
Audit dependency-injection registrations in a .NET solution. Use when: auditing DI registrations, finding missing bindings, composition-root review, or detecting lifetime mismatches (Singleton depending on Scoped, etc.). Produces a layered report of every registered service, missing interfaces, unresolved…
Skill Claude CodeCodex
C# XML documentation generator. Use when: adding XML doc comments, documenting public APIs, fixing CS1591 warnings, or improving documentation quality in .cs files. Takes a file path or type name as input.
Skill Claude CodeCodex
Repo-wide classification of exception handling patterns. Use when: auditing exception handling, finding swallowed exceptions, classifying catch patterns, finding overly-broad catches, or mapping unhandled-at-boundary throw sites in a C# solution. Optionally takes an exception type name to filter the audit.
Skill Claude CodeCodex
Diagnostic explainer and fixer. Use when: understanding a C# compiler error or warning, finding fixes for diagnostics, batch-fixing all instances of a diagnostic, or troubleshooting build failures. Takes a diagnostic ID (e.g., CS0246) or file:line as input.
Skill Claude CodeCodex
Extract method refactoring. Use when: extracting a block of statements into a new method, reducing method complexity, or breaking up long methods. Describe the code region and target method name as input.
Skill Claude CodeCodex
Whole-solution formatting compliance pass. Use when: enforcing whole-solution formatting, running dotnet format equivalents, bulk-organizing usings, or performing an editorconfig compliance sweep. Optionally takes a project name or file glob to narrow scope.
Skill Claude CodeCodex
Batch-scaffold test stubs for untested public APIs. Use when: batch-scaffolding tests for untested public APIs, generating test stubs, or bootstrapping a test project. Takes a top-N count, a project name, or a type name.
Skill Claude CodeCodex
Pre-change blast-radius report for a C# symbol. Use when: planning a rename, signature change, or deletion and you need to know how far the change reaches before touching code. Takes a symbol name (and optional change type) as input. Produces a ranked safe-to-change verdict with direct references, semantic consumers…
Skill Claude CodeCodex
Walk the inheritance and member-override graph for a type or member. Use when: exploring type hierarchies, finding overrides, finding implementations, understanding polymorphic dispatch, auditing interfaces. Takes a type or member name as input.
Skill Claude CodeCodex
Consumer-facing audit of the Roslyn MCP server's live surface against a loaded C# repo. Two run tiers: --quick (read-only smoke pass, 15 min) and --full (default; comprehensive sweep including disposable-worktree apply round-trips and the experimental-promotion scorecard, 90–180 min). Findings print to stdout by…
Skill Claude CodeCodex
NuGet package migration. Use when: replacing one NuGet package with another across a solution, upgrading packages, or migrating from deprecated packages. Takes old package name, new package name, and new version as input.
Skill Claude CodeCodex
Staged codebase modernization. Use when: systematically modernizing a C# codebase toward a stated goal, migrating between patterns/attributes/APIs at scale, or adopting newer language features (file-scoped namespaces, primary constructors, collection expressions) across many files. Takes a natural-language…
Skill Claude CodeCodex
Pre-NuGet-publish readiness check. Use when: preparing to publish to NuGet, checking release readiness for a .NET library, or validating package metadata, build, tests, and vulnerabilities before a release cut. Optionally takes a project name to narrow the scope.
Skill Claude CodeCodex
MSBuild and project-file inspection. Use when: debugging TargetFramework, OutputPath, package references, item includes, or evaluated MSBuild properties for a .csproj.
Skill Claude CodeCodex
Guided refactor → preview → apply → validate loop using v1.17/v1.18 primitives. Use when: implementing a non-trivial refactor that benefits from explicit staging through preview, apply-with-verify, and the validateworkspace bundle. Pairs well with the refactor skill for upstream symbol-level work.
Skill Claude CodeCodex
Guided semantic refactoring. Use when: renaming symbols, extracting interfaces, extracting types, moving types between files or projects, splitting classes, or performing bulk type replacements in C# code. Describe the desired refactoring as input.