code-actions

List and apply Roslyn code actions at a specified code span.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill code-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-actions
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/code-actions
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill code-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roslyn code actions (fixes and refactorings) exposed by the MCP host can be listed at a span, previewed, applied with the preview token, then validated.

Core Features & Use Cases

  • List available code actions at a given file span and preview diffs.
  • Apply a chosen action with a preview token and verify results via the MCP workflow.
  • Supports single-span and selection-range refactorings, including introducing parameters or inline temporaries.

Quick Start

Provide a file path and a target span to list actions, preview the diff, and apply the selected code action.

Frequently Asked Questions about code-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preview and apply Roslyn code actions at a specific span?

To apply Roslyn code actions, you provide a file path and target span to list available fixes, preview the diff, and then apply the chosen action using the preview token.

What are Roslyn code actions used for in code editing?

Roslyn code actions are used for automated code fixes and refactorings, allowing developers to view available actions at a span, preview diffs, and safely apply changes like introducing parameters or inline temporaries.

How do I apply a refactoring like introducing a parameter using Roslyn?

You apply a refactoring by providing the file path and selection range to list actions, previewing the diff, and applying the chosen code action with its preview token before validating the results.

Does this MCP host workflow support post-action validation for code edits?

Yes, the workflow supports post-action validation by requiring a preview before applying any code action, ensuring step-by-step guidance and verification of the applied refactoring results.

Why do I need a preview token to apply a code fix?

A preview token is required to enforce a safe workflow, ensuring you review the diff of the Roslyn code action before applying it and validating the post-action results.