research_codebase

Document modules, dependencies, and interactions in a read-only codebase map.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill research-codebase-brightblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research_codebase
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/research_codebase
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill research-codebase-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document and map an existing codebase for historical context using a thoughts directory; read-only; produces a structured artifact.

Core Features & Use Cases

  • Create a comprehensive map of modules, dependencies, and interactions as-is.
  • Preserve decisions and research in thoughts directory for future reference.
  • Use case: When onboarding a new engineer, generate an up-to-date software map to accelerate understanding.

Quick Start

Provide a research question or scope, and I will generate a document that maps the codebase and relevant thoughts.

Frequently Asked Questions about research_codebase

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

FAQPage Schema
How do I document an existing codebase for new engineer onboarding?

To document an existing codebase for onboarding, you can generate a comprehensive map of modules, dependencies, and interactions that accurately reflects the current state of the software architecture.

What is the best way to map cross-component relationships without modifying source code?

Mapping cross-component relationships without modifying source code requires a read-only analysis approach that identifies historical decisions and interactions, preserving them as structured artifacts for future reference.

How do I generate architecture documentation that captures current codebase patterns?

Generating architecture documentation that captures current codebase patterns involves analyzing the codebase as-is to identify modules and interactions, then storing the structured research artifacts in a designated thoughts directory.

Can I use a codebase research tool to analyze dependencies and store results in a thoughts directory?

Yes, you can use a read-only codebase research tool to analyze dependencies and interactions, producing structured artifacts that adhere to the thoughts schema and are stored directly in the thoughts directory.

Does codebase analysis work without altering the original source files?

Codebase analysis works without altering original source files by using a strictly read-only approach to examine modules, dependencies, and historical decisions while storing the resulting documentation separately.

What format do the artifacts produced by codebase research need to follow?

The artifacts produced by codebase research must adhere to the thoughts schema and be stored in the designated thoughts directory to ensure the documentation is structured for future reference.