rmc-find-symbol

Resolve ambiguous Rust symbol hints into exact qualified names for hypergraph queries.

29|5|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-find-symbol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rmc-find-symbol
Source: https://github.com/molaco/rust-code-mcp/tree/main/skills/rmc-find-symbol
Command: npx skills add https://github.com/molaco/rust-code-mcp --skill rmc-find-symbol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn an imprecise hint—like a symbol fragment, a path, or a vague description—into the exact qualified Rust symbol name required to run structural hypergraph queries.

Core Features & Use Cases

  • Find candidate symbols quickly: Use Rust-aware definition lookup or high-recall search to locate likely matches from limited context (e.g., fragment, log message, doc string).
  • Confirm the exact location: Validate candidate declarations by pulling file/line results and then reading the source file contents for confirmation.
  • Derive the qualified name reliably: Convert file paths and module structure into the <crate>::<module_path>::<item_name> format, including inner items like ::<TypeName>::<method>.
  • Promote into hypergraph analysis: Once the qualified name is known, hand off to relationship queries like imports/uses to continue deeper forensics.

Quick Start

Ask the skill to resolve your input by returning the qualified name and a one-line explanation of how it was resolved.

Frequently Asked Questions about rmc-find-symbol

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

FAQPage Schema
How do I resolve a vague Rust symbol fragment into an exact qualified name?

To resolve a Rust symbol fragment into an exact qualified name, the skill uses rust-analyzer driven candidate discovery to locate likely matches, then validates the source contents to derive the precise crate, module path, and item name.

How do I find the qualified name of a Rust method from a file path?

Finding the qualified name from a Rust file path involves deriving the module structure from the path, reading the source content to validate declarations, and formatting the result as crate::module_path::TypeName::method.

Can I use rust-analyzer search results to prepare data for hypergraph structural queries?

Yes, you can use rust-analyzer search results to prepare for hypergraph structural queries by promoting ambiguous symbol hints, file paths, or doc strings into deterministic qualified names required by downstream relationship analysis.

What is the best way to identify a Rust symbol when I only have a log message or doc string?

The best way to identify a Rust symbol from a log message or doc string is applying high-recall rust-aware search to locate candidate declarations, validating the exact file and line, and converting the module structure into a qualified name.

Does resolving a Rust qualified name require manually checking the module tree?

Resolving a Rust qualified name does not require manual module tree checks; the process automatically derives the path-to-module hierarchy and validates inner items to produce a deterministic qualified name for downstream forensics.