Generate a structured codebase research document with file:line references.
npx skills add https://github.com/aldengolab/lorist --skill research-report-aldengolab
Please help me install this Agent Skill. Skill: research-report Source: https://github.com/aldengolab/lorist/tree/main/skills/research-report Command: npx skills add https://github.com/aldengolab/lorist --skill research-report-aldengolab
Produces a purely descriptive technical map of a codebase, documenting what exists, where it lives, and how it connects — without evaluating or suggesting changes.
Provide a path to the codebase and I will generate a structured research document with file:line references.
High-intent search queries and answers about installing and using this skill.
Mapping a codebase involves enumerating directories, key interfaces, and component connections with file:line references. This generates a structured markdown document detailing what exists and how dependencies flow, enabling you to understand scope before modifying features.
The best way to document code structure for onboarding is generating a descriptive technical map with explicit file:line references. This outlines how components connect and data flows without modifying code, producing a navigable research document for new developers.
Yes, you can generate architecture documentation that is purely descriptive and explicitly avoids evaluation or suggestions. It documents what exists, where it lives, and how components connect, providing a neutral technical map for your research.
Yes, the generated research document includes explicit file:line references throughout its structured areas. This ensures precise code navigation by mapping exactly where components exist and connect within the codebase directories and interfaces.
You need a descriptive codebase map when starting a new feature, onboarding a team member, or conducting upfront architecture studies to understand scope. Unlike a code review, it purely documents what exists and how components connect without evaluating or suggesting changes.
VMRam95Analyze directory structures and source code to generate hierarchical documentation and architectural maps.
CygnusfearCreate modular Obsidian-compatible markdown wikis for project plans.
nathanvaleQuery a codebase call graph for blast radius and dead code analysis.
plastikawebGenerate Markdown documentation, API references, and architecture guides from codebases.
