Generates concise Rust codebase maps for efficient navigation and planning.
npx skills add https://github.com/tfunk1030/vibe --skill rp-explorer-tfunk1030
Please help me install this Agent Skill. Skill: rp-explorer Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/rp-explorer Command: npx skills add https://github.com/tfunk1030/vibe --skill rp-explorer-tfunk1030
Onboarding developers and planning work in brownfield projects is time-consuming due to the need to read many files and infer structure. rp-explorer provides a token-efficient overview by generating a concise codebase map that highlights structure, signatures, and relevant files.
Ask RepoPrompt to generate a concise codebase map for the current project.
High-intent search queries and answers about installing and using this skill.
You can understand an existing codebase by generating a token-efficient codebase map that reveals tree structures and file signatures without bulk reads. This approach minimizes reading time and highlights relevant files for quick onboarding.
Planning features in a brownfield project is best done by extracting a token-efficient codebase map. Using CLI commands to generate file and region signatures reveals the project layout needed to guide planning and debugging.
Yes, you can search for specific code signatures within a repository using CLI search commands. This allows you to query repository information and extract relevant file regions without loading the entire codebase into context.
RepoPrompt works for understanding project layout and debugging by providing CLI commands like tree, structure, and read. These tools organize repository information into actionable maps for quick assessment of brownfield code.
To export codebase context for onboarding developers, use the builder and context commands. These tools extract and organize repository information into a token-efficient map that highlights structure and signatures for new team members.
The limitation of generating a codebase map for large repositories is the reliance on token efficiency to avoid context limits. By extracting signatures and structures instead of bulk reads, it minimizes tokens but may omit granular implementation details.
ZESCODESearch git commit logs and inspect code patterns across ZES system repositories.
babuallyMap unfamiliar code into a broader architectural view with modules and callers.
estaciolimaAutomate Git staging and commits after Spec Kit lifecycle events.
JaronTamScan and analyze brownfield project structures to generate structured documentation.
