roslyn-mcp

Plugin roslyn-mcp from marketplace roslyn-mcp-marketplace in darylmcd/Roslyn-Backed-MCP. Commands read from the repo's manifest — today.

Skills (41)

• backlog-intake

  Consolidate deep-review artifacts (mcp-server-audit, experimental-promotion, roslyn-mcp-retro) into ai_docs/backlog.md with anchor verification, dedupe, priority classification, and sizing for remediation sessions (`~/.claude/prompts/remediate.md`). Use when: a deep-review / audit wave has produced

• bump

  Version bump. Use when: bumping the version for a release, preparing a version increment (major/minor/patch), or when code changes require a new version. Takes bump type as input: 'major', 'minor', or 'patch'. Edits all 7 version files, consumes `changelog.d/*.md` fragments into a new `## [X.Y.Z]` s

• mcp-server-stress

  Maintainer-only thin alias for `/mcp-server-surface-test --output-mode=fragments`. Repo-local skill (lives under `.claude/skills/`, only discoverable from a Claude Code session whose project root is Roslyn-Backed-MCP). Invokes the canonical audit prompt at `${CLAUDE_PLUGIN_ROOT}/skills/mcp-server-su

• promote-tier

  Flip a tool, resource, or prompt's support tier between `stable` and `experimental` atomically across both source-of-truth sites (`[McpToolMetadata]` annotation and `ServerSurfaceCatalog` partial entry). Use when: `/publish-preflight` Step 8 surfaces a `recommendation: \"promote\"` row in the promot

• publish-preflight

  Pre-publish validation checklist. Use when: preparing to publish to NuGet, validating release readiness, or running the full pre-publish pipeline. Checks version drift, AI docs, build/test/publish, changelog, security versions, and doc-audit freshness.

• reconcile-backlog-vs-issues

  Audit every `gh #NNN` reference in `ai_docs/backlog.md` against live GitHub Issue state and emit a 5-state triage report. Use when: chasing drift between backlog rows and Issues after merges, manual issue closures, label changes, or contributor inactivity; before `/backlog-remediate` to surface zomb

• recover-stalled-subagent

  Recover a stalled subagent's uncommitted worktree into a WIP branch and remove the worktree cleanly in one invocation. Use when: a subagent returned a malformed or empty final result and its `.worktrees/<id>` still contains uncommitted work that must not be lost. Takes the remediation branch name (w

• release-cut

  Atomic release pipeline — bump -> verify -> ship -> tag -> refresh-plugin. Use when cutting a major/minor/patch release. Delegates to /bump, /ship, and the maintainer-local /update; checkpointed so mid-flow failure is re-runnable.

• surface-audit

  One-pass audit of the Roslyn MCP server's live surface (tools / resources / prompts / shipped skills) against documentation count claims. Use when preparing a release, chasing doc drift, or answering "how many tools does this server have?" without burning a dozen greps. Calls server_info, globs skil

• update

  Maintainer-local override of the shipped /roslyn-mcp:update skill. Refreshes both install layers from this checkout — the Layer 2 plugin cache with its release-pinned dnx server launch, and the Layer 1 global tool — then verifies both track the same version.

• analyze

  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.

• architecture-review

  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.

• code-actions

  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.

• complexity

  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.

• dead-code

  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.

• di-audit

  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, unre

• document

  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.

• exception-audit

  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

• explain-error

  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.

• extract-method

  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.

• format-sweep

  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.

• generate-tests

  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.

• impact-assessment

  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, s

• inheritance-explorer

  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.

• mcp-server-surface-test

  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

• migrate-package

  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.

• modernize

  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-l

• nuget-preflight

  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.

• project-inspection

  MSBuild and project-file inspection. Use when: debugging TargetFramework, OutputPath, package references, item includes, or evaluated MSBuild properties for a .csproj.

• refactor-loop

  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 validate_workspace bundle. Pairs well with the refactor skill for upstream symbol-level work.

• refactor

  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.

• review

  Semantic code review. Use when: reviewing C# code quality, finding issues before a PR, auditing a file or project for problems, or doing a comprehensive quality check. Optionally takes a file path or project name as input.

• security

  Security audit for C# solutions. Use when: auditing for vulnerabilities, checking NuGet packages for CVEs, reviewing security diagnostics, finding reflection usage, auditing DI registrations, or doing an OWASP-style security review. Optionally takes a project name.

• semantic-find

  Natural-language code search across a C# codebase. Use when: looking for a class, method, or pattern described in plain English (e.g. 'the class that handles payment refunds', 'methods that retry on failure'), locating code by behavior rather than exact name, or orienting in an unfamiliar solution.

• session-undo

  Session history and undo. Use when: the user wants to see what Roslyn MCP changed, undo the last apply, reload the workspace from disk, or recover from a bad refactoring.

• snippet-eval

  Quick C# feedback without loading a solution. Use when: validating syntax, semantics, or running a small script; prototyping an expression; or explaining an isolated code fragment.

• test-coverage

  Test coverage analysis. Use when: checking test coverage, finding untested code, identifying gaps in test suites, scaffolding new tests, or auditing which public APIs have tests. Optionally takes a project name.

• test-triage

  Test discovery and failure triage. Use when: CI is red, tests fail locally, or you need to find and run the right tests after a change. Optionally takes project name or filter.

• trace-flow

  Walk a value, parameter, or symbol through control flow, data flow, and exception flow paths. Use when: tracing a value through control/data/exception flow, understanding how a parameter propagates, finding where an exception is caught, or answering 'where can this value go?' / 'what paths does cont

• version-bump

  Multi-project version bump across a .NET solution. Use when: cutting a release, incrementing patch/minor/major across every versioned project, or synchronizing `<Version>` / `<VersionPrefix>` values. Takes a bump type (patch, minor, or major) as input. Edits MSBuild version properties across all pro

• workspace-health

  One-shot status report on the running Roslyn MCP server and any loaded workspaces. Use when: troubleshooting the server, onboarding a session, confirming readiness before a sensitive operation, listing loaded workspaces, checking for staleness/degraded state, or recovering from `Server \"roslyn\" is

Subagents (1)

• audit-phase-runner

  Run one context-heavy /mcp-server-surface-test 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 refac

Hooks (2)

• PostToolUse
• PostToolUse

Similar plugins