Use rust-doctor as a /rust-doctor slash command in Claude Code — no MCP setup required.

What is a Claude Code skill?

A Claude Code skill is a reusable workflow that extends Claude's capabilities via slash commands. Unlike MCP servers, skills require no background process, no configuration, and no server setup.

The rust-doctor skill gives you a /rust-doctor slash command that runs the full scan pipeline, interprets results, and provides actionable fix guidance — all from within Claude Code.

Installation

Via setup wizard (recommended):

rust-doctor setup

The wizard detects Claude Code and Cursor, then installs the skill automatically. Choose "CLI + Skills" when prompted.

Or via npx:

npx skills add https://github.com/ArthurDEV44/rust-doctor --skill rust-doctor

Or copy manually:

cp -r skills/rust-doctor/ ~/.claude/skills/rust-doctor/

The skill requires the rust-doctor CLI to be installed. If you haven't installed it yet:

cargo install rust-doctor
# or
npm install -g rust-doctor

Usage

/rust-doctor                          # scan current project
/rust-doctor /path/to/project         # scan a specific directory
/rust-doctor --diff                   # scan only changed files
/rust-doctor --diff main              # scan changes vs main branch
/rust-doctor --fix                    # scan + apply fixes (asks before modifying)
/rust-doctor --plan                   # scan + prioritized remediation plan
/rust-doctor --score                  # quick score only
/rust-doctor --sarif                  # SARIF output for CI integration
/rust-doctor --offline                # skip network checks
/rust-doctor --project core,api       # scan specific workspace members

How it works

The skill runs a 4-step pipeline:

Scope — detects the project, resolves the rust-doctor binary, and parses your flags
Scan — runs rust-doctor --verbose --json and captures the output
Interpret — parses the JSON, categorizes findings by priority (CRITICAL / HIGH / MEDIUM / LOW)
Guide — reads flagged files, explains each issue, provides before/after code fixes, and re-scans to verify improvement

Skill vs MCP

	Skill (`/rust-doctor`)	MCP server (`--mcp`)
Setup	Copy one folder	Configure `settings.json` or `.mcp.json`
Invocation	User-initiated via `/rust-doctor`	Claude decides when to call tools
Context	Runs in isolated fork — no conversation pollution	Tools available throughout conversation
Output	Structured report with fix guidance	Raw diagnostics for Claude to interpret
Best for	On-demand health checks, fix workflows	Continuous AI-assisted development

Both approaches use the same rust-doctor CLI and produce identical scan results. Choose based on your workflow preference.

Skill contents

skills/rust-doctor/
├── SKILL.md                           # Main skill (slash command entry point)
└── references/
    ├── rules-reference.md             # All 19 rules with fix strategies
    ├── score-interpretation.md        # Score calculation and dimension weights
    └── suppression-syntax.md          # Inline suppression + config options

Claude Code Skill