rara-codebase

Generate a subsystem-aligned repository map with file-by-file reading paths.

15|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/linkerdog/rara --skill rara-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rara-codebase
Source: https://github.com/linkerdog/rara/tree/main/.agents/skills/rara-codebase
Command: npx skills add https://github.com/linkerdog/rara --skill rara-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Understanding a large codebase quickly is hard when you need to know where subsystems live, how files relate, and what to read next.

Core Features & Use Cases

  • Subsystem-first codebase mapping: Provides a one-line, file-by-file index grouped by memory, context, hooks, runtime, agent, LLM, tools, and TUI.
  • Navigation optimized for rapid comprehension: Helps you identify entry points and mental-model boundaries (e.g., how context assembly flows into memory selection and prompt construction).
  • Use case: When you need to implement a feature or debug behavior, you can quickly find the exact Rust modules and related crates to inspect (such as the memory retrieval pipeline or the hook discovery mechanism).

Quick Start

Ask for the codebase map, then request the exact files you should read to understand how a specific capability works, such as "Where is the effective prompt assembled and how does it inject memory and hooks?"

Frequently Asked Questions about rara-codebase

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

FAQPage Schema
How do I navigate a large Rust codebase to understand where subsystems are implemented?

To navigate a Rust codebase, you can use a subsystem-first codebase map that indexes modules and crates by role. This translates repository file structure into reading paths, helping you locate major subsystems and their connections quickly.

What's the best way to map out a repository for developer onboarding?

Mapping out a repository for onboarding is best done by grouping files into a deterministic, repository-index style map. This provides a file-by-file index grouped by subsystems like memory, runtime, and tools to identify entry points and boundaries.

How do I find the exact Rust modules to inspect when debugging feature behavior?

To find exact Rust modules for debugging, request a codebase map to identify the subsystem involved. It enumerates relevant modules and their roles, allowing you to pinpoint specific crates like the memory retrieval pipeline or hook discovery mechanism.

Does this codebase navigation approach work for planning refactors across multiple modules?

Yes, codebase navigation works for refactoring by providing a clear map of how files connect across subsystems. It helps you understand mental-model boundaries and trace flows like context assembly into memory selection, ensuring comprehensive refactor planning.

How do I use a codebase map to trace how a prompt is assembled and injects memory?

To trace prompt assembly, ask the codebase map for the exact files detailing context assembly flows. It identifies the specific Rust modules where memory selection, hook integration, and prompt construction connect.

Do I need a YAML-defined configuration to generate a subsystem codebase map?

Yes, generating a subsystem codebase map requires YAML-defined discoverability fields. These fields structure the deterministic repository index that enumerates relevant modules, ensuring the codebase navigation output is accurately aligned.