# Navigate Code With Repo Maps

Large repositories make symbol lookup slow and repetitive. This skill adds repo-map MCP tools that index project symbols and retrieve relevant code context quickly.

## Install

```bash
npx skillstore add chipflow/claude-plugin
```

## Metadata

- Status: approved
- Slug: chipflow-claude-plugin
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4c8d451d00dbdb6b3f7d965aa3629926d82c8a85dc3417429e8bbdbccd8d11cb
- Author: ChipFlow
- GitHub username: ChipFlow
- License: MIT
- Repository: https://github.com/ChipFlow/claude-context-tools/tree/main/.claude-plugin
- Ref: dd4a3ef9f20ddf38830950b4bb713df96b431fd6
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/chipflow-claude-plugin
- Manifest: https://skillstore.pages.dev/api/skills/chipflow-claude-plugin/manifest

## Capabilities

- Searches functions, classes, and methods by symbol name pattern through repo-map MCP tools.
- Lists indexed symbols for a selected file.
- Retrieves source content for an indexed symbol by exact name.
- Refreshes the repository symbol map and reports indexing status.
- Waits for background indexing and reports stale or failed indexes.
- Uses per-project .claude repo-map files when switching working directories.

## Use Cases

- Find symbol definitions quickly: Locate functions, classes, and methods by name pattern before reading full files.
- Review large repositories: Build a fast map of important symbols and files before reviewing a change.
- Prepare safer refactors: Refresh the symbol index and compare related definitions before moving or rewriting code.

## Prompt Templates

### Find a symbol pattern

```
Use the repo-map tools to search for symbols matching parse_* and summarize the best matches.
```

### Inspect one file

```
List the symbols in src/models/user.py, then identify which classes or functions I should inspect first.
```

### Trace a feature entry point

```
Search for handler symbols related to billing, fetch the most relevant symbol content, and explain the control flow.
```

### Refresh before refactoring

```
Check repo-map status, reindex if stale, wait for completion, and compare overlapping symbols before I refactor.
```

## Limitations

- Requires Claude Code plugin installation and a session restart before MCP tools are available.
- Symbol indexing is documented for Python, C\+\+, and Rust.
- It does not replace full-text search for comments, strings, or unsupported languages.
- It creates local .claude index, manifest, learning, and log files inside projects.

## Best Practices

- Restart Claude Code after installing or updating the plugin.
- Use symbol search for names and standard search for file content.
- Review .claude artifacts before sharing a project archive.

## Anti Patterns

- Do not assume unsupported languages are fully indexed.
- Do not rely on stale repo-map results after large code changes.
- Do not index repositories with secrets without checking local storage policy.

## Security Audit

- Audited at: 2026-07-06T05:58:40.781\+00:00
- Summary: Most static command and network findings are false positives from Markdown examples or repository metadata. The confirmed risk is local project access: the plugin starts a repo-map MCP server, indexes the active project, and stores symbol metadata in hidden .claude files. I found no evidence of prompt injection or remote data exfiltration in the reviewed files.

## Stats

- Views: 209
- Downloads: 8
- Favorites: 0
- Popularity score: 0