Agent skill

Analyze Using Rustrover

by illegalstudio in illegalstudio/elephc

Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues.

MITAuto-check passedDevelopment

Install Analyze Using Rustrover

skills CLI
$ npx skills add illegalstudio/elephc --skill analyze-using-rustrover -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install illegalstudio/elephc analyze-using-rustrover --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/illegalstudio/elephc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/analyze-using-rustrover .claude/skills/analyze-using-rustrover && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyze-using-rustrover
GitHub stars
602
Token cost
~932 tokens
SKILL.md length
298 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues.

  • Works in 5 steps: Discover all source files → Errors pass → Warnings pass → …
  • Tasks that involve Code quality
  • SKILL.md covers Scope, Steps, Output Format and Important
  • Calls cargo

What it does

Analyze Using Rustrover is an agent skill from illegalstudio/elephc. Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code quality. It works with Model Context Protocol. The repository describes itself as: A PHP-to-native compiler. Takes a subset of PHP - including eval() - and compiles it directly to native assembly, producing standalone binaries for macOS ARM64, Linux ARM64, and… The licence is MIT.

When your agent uses it

  • Tasks that involve Code quality

Example prompts

  • “/analyze-using-rustrover”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Discover all source files
  2. Errors pass
  3. Warnings pass
  4. Verify with compiler
  5. Also analyze tests and main

What it can do on your machine

Read from SKILL.md and the folder at commit afbb2af. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze Using Rustrover loads about 932 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 298 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~932

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from illegalstudio/elephc at commit afbb2af, republished under its MIT licence (© illegalstudio). 298 words, ~932 tokens.

Download SKILL.mdSave it as .claude/skills/analyze-using-rustrover/SKILL.md (or your agent's skills folder).
name
analyze-using-rustrover
description
Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues.
user-invocable
true

Analyze Using RustRover

You are a code quality analyst. Use the RustRover MCP tools to inspect the elephc codebase and produce a structured report.

Scope

By default, analyze all .rs source files in the project. If the user specifies a file or directory, limit the analysis to that scope.

Steps

1. Discover all source files

Use the Glob tool to find every .rs file in the project:

pattern: "src/**/*.rs"

This ensures the analysis covers all files, including any newly added modules.

2. Errors pass

Run mcp__rustrover__get_file_problems with errorsOnly: true on every discovered .rs file. Always pass projectPath set to the current working directory.

Batch calls in parallel (up to 6 per message) to save time. Use relative paths from the project root (e.g., src/codegen/mod.rs).

Collect all errors.

3. Warnings pass

Run mcp__rustrover__get_file_problems with errorsOnly: false on every discovered .rs file.

Batch calls in parallel. Collect all warnings.

Categorize warnings into:

  • Duplicated code: note the file, line, and fragment length
  • Unnecessary path prefixes: note the file and the prefix that could be simplified
  • Other warnings: anything else RustRover flags
4. Verify with compiler

Run these commands to cross-validate RustRover findings:

bash
cargo build 2>&1 | tail -5
cargo clippy 2>&1 | grep "warning:" | grep -v "generated"

This confirms whether RustRover errors are real or false positives. RustRover sometimes fails to resolve impl blocks in large files — if cargo build succeeds, those are false positives.

5. Also analyze tests and main

Include src/main.rs and all files in tests/ in the analysis:

pattern: "tests/**/*.rs"

Output Format

## RustRover Inspection Report

**Files analyzed:** N

### Build Validation
- `cargo build`: CLEAN / N warnings
- `cargo clippy`: CLEAN / N warnings
- Clippy details: (list if any)

### Real Errors
(Errors confirmed by both RustRover and cargo build)

| File | Line | Severity | Description |
|------|------|----------|-------------|
| ... | ... | ERROR | ... |

If none: "No real errors found."

### False Positives
(RustRover errors that cargo build does not reproduce)

| File | Count | Likely cause |
|------|-------|-------------|
| ... | ... | Large file / impl block resolution |

### Code Quality Warnings

#### Duplicated Code
| File | Line | Fragment length | Description |
|------|------|-----------------|-------------|
| ... | ... | N lines | ... |

Summary: N duplicated fragments across M files. Top candidates for extraction: (list the most impactful)

#### Unnecessary Path Prefixes
| File | Line | Current | Suggested |
|------|------|---------|-----------|
| ... | ... | `self::functions::` | `functions::` |

#### Other Warnings
| File | Line | Description |
|------|------|-------------|
| ... | ... | ... |

### Summary
- Files analyzed: N
- Real errors: N
- False positives: N
- Code quality warnings: N (M duplications, K path prefixes, J other)
- Recommendation: (actionable next steps if any)

Important

  • Discover files dynamically with Glob — never use a hardcoded file list
  • Run inspections in parallel to save time (batch up to 6 files per tool call)
  • Always cross-check RustRover errors with cargo build — false positives are common on large files
  • Do NOT fix any code. Only report findings.
  • If no MCP RustRover tools are available, inform the user and suggest running cargo clippy instead

© illegalstudio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/analyze-using-rustrover of illegalstudio/elephc.

Open the folder on GitHubat commit afbb2af

Compare with similar skills

Analyze Using Rustrover next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyze Using Rustrover compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze Using Rustrover this skillillegalstudio/elephc602—~932Automated safety check: PassMIT
Graph-Guided Safe Refactoringtirth8205/code-review-graph32k1 repos~332Automated safety check: PassMIT
Mariadb Operator PR Reviewmariadb-operator/mariadb-operator1k—~3.3kAutomated safety check: PassApache-2.0
Codex Code ReviewerVCnoC/Claude-Code-Zen-mcp-Skill-Work116—~3.5kAutomated safety check: PassApache-2.0
Refactortermide/termide171—~2.8kAutomated safety check: PassMIT
RAG Code Reviewlyonzin/knowledge-rag290—~1.8kAutomated safety check: PassMIT

Similar skills

  • Graph-Guided Safe Refactoring

    tirth8205/code-review-graph

    Plans a refactor from a code dependency graph, previews renames before applying them and checks that the final impact matches the plan.

    32k GitHub starsUsed in 1 repo~332 tokens
    DevelopmentAuto-check passed
  • Mariadb Operator PR Review

    mariadb-operator/mariadb-operator

    Perform a structured maintainer-style PR review for the mariadb-operator repository.

    1k GitHub stars~3.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Codex Code Reviewer

    VCnoC/Claude-Code-Zen-mcp-Skill-Work

    Systematic code review workflow using zen mcp's codex tool. An agent skill from VCnoC/Claude-Code-Zen-mcp-Skill-Work.

    116 GitHub stars~3.5k tokensUpdated 9 mo ago
    DevelopmentAuto-check passed
  • Refactor

    termide/termide

    Full-workspace code quality analysis and refactoring with validation

    171 GitHub stars~2.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • RAG Code Review

    lyonzin/knowledge-rag

    When performing code review on a PR, diff, snippet, or "look at this change" request, first consult the corpus for related ADRs, coding standards, prior patterns, and similar files.

    290 GitHub stars~1.8k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Cao Contributing

    awslabs/cli-agent-orchestrator

    Official

    Contribute changes to the CAO (CLI Agent Orchestrator) codebase — the local dev loop, the CI gate map, and the pre-PR checklist.

    1.4k GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed

More from illegalstudio/elephc

  • Prepare Release Changelog

    illegalstudio/elephc

    Audit and prepare Elephc's numbered release changelog from the last published GitHub release through an exact candidate main SHA.

    602 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Update Builtin Docs

    illegalstudio/elephc

    Regenerate and audit Elephc's generated builtin documentation from the shared builtin contract plus builtin!

    602 GitHub stars~633 tokensUpdated today
    Auto-check passed
  • Doc Update

    illegalstudio/elephc

    Audit and update the docs/ wiki to match the current codebase — checks all doc files against source code and fixes any mismatches.

    602 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Verify Release

    illegalstudio/elephc

    Pre-release verification that first requires a complete release-changelog audit, then checks README, docs, roadmap, test coverage, examples, and the full test suite for regressions.

    602 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Analyze Using Rustrover

What does Analyze Using Rustrover do?

Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues. Analyze Using Rustrover is an agent skill from illegalstudio/elephc. Run RustRover IDE inspections on the codebase and produce a structured report of errors, warnings, and code quality issues.

When should I use Analyze Using Rustrover?

Analyze Using Rustrover fits situations like: tasks that involve Code quality.

How do I install Analyze Using Rustrover in Claude Code?

Run `npx skills add illegalstudio/elephc --skill analyze-using-rustrover -a claude-code`. Or copy the skill folder (.claude/skills/analyze-using-rustrover in illegalstudio/elephc) into .claude/skills/analyze-using-rustrover in your project. Claude Code loads it when a task matches its description.

How do I install Analyze Using Rustrover in Codex?

Run `npx skills add illegalstudio/elephc --skill analyze-using-rustrover -a codex`. Or copy the skill folder (.claude/skills/analyze-using-rustrover in illegalstudio/elephc) into .agents/skills/analyze-using-rustrover in your project. Codex loads it when a task matches its description.

Can I use Analyze Using Rustrover in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add illegalstudio/elephc --skill analyze-using-rustrover -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-using-rustrover, .gemini/skills/analyze-using-rustrover, .github/skills/analyze-using-rustrover and .opencode/skills/analyze-using-rustrover in your project.

What does Analyze Using Rustrover need to run?

Going by SKILL.md and its folder, Analyze Using Rustrover needs the command-line tools its instructions call (cargo).

Does Analyze Using Rustrover access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analyze Using Rustrover safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analyze Using Rustrover use?

Analyze Using Rustrover is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze Using Rustrover use?

About 932 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze Using Rustrover?

Skills that share tags, products or a category with Analyze Using Rustrover: Graph-Guided Safe Refactoring (tirth8205/code-review-graph, 32k stars), Mariadb Operator PR Review (mariadb-operator/mariadb-operator, 1k stars), Codex Code Reviewer (VCnoC/Claude-Code-Zen-mcp-Skill-Work, 116 stars) and Refactor (termide/termide, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze Using Rustrover?

illegalstudio (a GitHub organization) maintains it in illegalstudio/elephc, which has 602 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

Source: illegalstudio/elephc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.