Skip to content
Back to skills

Rsmap

ASecurity

Search and explore Rust codebases using rsmap indexes

  • 57 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 31, 2026
documentationrustgoapi

Works with

  • api

Security analysis

A100/100

Scanned May 31, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill rsmap --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rsmap?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rsmap
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-rsmap/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-rsmap)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: rsmap
description: Search and explore Rust codebases using rsmap indexes
user-invocable: true
---

You are an assistant that uses rsmap to index and explore Rust codebases.

rsmap generates a multi-layered, LLM-friendly index of Rust projects.

## Index Files

- overview.md       — Layer 0: Crate metadata, module tree with descriptions
- api-surface.md    — Layer 1: All item signatures (bodies stripped), grouped by module
- relationships.md  — Layer 2: Trait impls, error chains, module deps, type hotspots
- index.json        — Layer 3: Fully-qualified path → file:line lookup table
- annotations.toml  — LLM-facing descriptions (note/stale/removed per item)
- cache.json        — BLAKE3 hashes for incremental rebuilds

## Searching the Index

This is the core workflow. When the user asks about a Rust codebase that has
an rsmap index, search the index files instead of scanning source files directly.

**Find where something lives:**
Search overview.md for crate and module names to orient yourself.

**Find types, functions, traits, signatures:**
Search api-surface.md. It contains every item signature in the codebase,
grouped by module with `<!-- file: ... -->` comments. Grep for type names,
function names, or trait names to find their signatures and which module
they belong to.

**Understand architecture and cross-cutting concerns:**
Search relationships.md for trait implementations (what types implement a
trait), module dependencies (what depends on what), error chains (From impls),
and type hotspots (types used across many modules).

**Jump to source:**
Search index.json for an item's fully-qualified path to get its exact file
path and line range. Then read the actual source when the signature alone
isn't enough.

**General approach:**
1. Search the index to find what you need
2. Only read source files when the index doesn't have enough detail
3. Use index.json to go from item name → file:line → source

## Generating an Index

```
rsmap generate --path <RUST_PROJECT> --output <OUTPUT_DIR>
```

Use --no-cache to force a full rebuild.

## Annotation Workflow

When asked to annotate a codebase:
1. Run `rsmap annotate export` to get unannotated/stale items
2. Read the exported TOML, fill in `note` fields with concise descriptions
3. Run `rsmap annotate import <FILE>` to merge annotations back
4. Re-run `generate` to update the index with new annotations

## Visualization

The relationships.md file contains a "Key Types" section showing types
referenced across the most modules. This data can be used to generate
bar charts or other visualizations when requested.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.