research_codebase_nt

Creates a reproducible, machine-readable map of codebase components and dependencies.

2|Updated May 8, 2026

Search Tags:#documentation #research #onboarding #codebase #mapping #read-only #code-structure

Ready to run

npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill research-codebase-nt-brightblock

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research_codebase_nt
Source: https://github.com/BrightBlock/hyprlayer-cli/tree/main/claude/skills/research_codebase_nt
Command: npx skills add https://github.com/BrightBlock/hyprlayer-cli --skill research-codebase-nt-brightblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document the current codebase state across components to create a reproducible map without performing evaluations or making recommendations.

Core Features & Use Cases

Create a machine-readable map of codebase components (directories, modules, and dependencies) for onboarding, auditing, and knowledge transfer.
Produce a read-only artifact that can be stored in the configured backend and shared with team members.

Quick Start

Provide a read-only documentation of the codebase as it exists today by spawning parallel research tasks and producing a non-evaluative artifact.

Frequently Asked Questions about research_codebase_nt

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

FAQPage Schema

How do I document codebase structure for onboarding without making code evaluations?▼

Documenting codebase structure without evaluations involves mapping directories, modules, and dependencies into a read-only, reproducible artifact. This maps the exact current state across components for onboarding and knowledge transfer.

What is a read-only codebase map and when do I need it?▼

A read-only codebase map is a machine-readable representation of current code structure and dependencies. You need it for auditing, onboarding, or knowledge transfer when you require reproducible documentation without architectural evaluations.

How do I generate reproducible code documentation for a non-standard directory layout?▼

Generate reproducible code documentation for non-standard layouts by spawning parallel research tasks across components. This produces a non-evaluative artifact mapping the codebase exactly as it exists today.

Can I map codebase dependencies and modules without modifying the source files?▼

Yes, you can map codebase dependencies and modules without modifying source files by producing a read-only artifact. This approach documents the current state while satisfying the requirement for non-evaluative documentation.

What's the best way to create a machine-readable map of codebase components for auditing?▼

The best way to create a machine-readable map for auditing is to document the current codebase state across components into a reproducible, read-only artifact. This avoids evaluations and maps directories and dependencies as they exist.