archivist

Map repository structure and module boundaries into navigable documentation.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/benediktms/overmind --skill archivist-benediktms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archivist
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/archivist
Command: npx skills add https://github.com/benediktms/overmind --skill archivist-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

archivist maps the repository structure, identifies module boundaries, and synthesizes navigable documentation to preserve knowledge for future contributors.

Core Features & Use Cases

  • Map repository structure and discover module boundaries to enable quick orientation for new contributors.
  • Generate navigable documentation, READMEs, and reference materials for onboarding and reviews.
  • Preserve knowledge for future changes and improve maintainability across codebases.

Quick Start

Run archivist on the target codebase to generate a navigable documentation map for onboarding.

Frequently Asked Questions about archivist

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

FAQPage Schema
How do I generate navigable documentation for onboarding new contributors to a codebase?

Generate navigable documentation by mapping the repository structure and identifying module boundaries. This produces navigable knowledge artifacts and reference materials that enable quick orientation for new contributors during onboarding.

What is codebase mapping and how does it help preserve knowledge for future changes?

Codebase mapping identifies module boundaries and repository structure to preserve knowledge for future contributors. It synthesizes navigable documentation that improves maintainability and prevents knowledge loss across multi-module projects.

Can I map module boundaries across multi-module projects with different documentation conventions?

Yes, mapping module boundaries across multi-module projects supports different documentation conventions. The process requires alignment with existing documentation conventions and verification of file references to ensure accurate knowledge synthesis.

What's the best way to discover module boundaries during codebase exploration?

The best way to discover module boundaries is mapping repository structure directly within the target codebase. This approach enables quick orientation by identifying module boundaries and synthesizing navigable documentation for reviews.

Do I need to verify file references when generating documentation maps for a repository?

Yes, verifying file references is required when generating documentation maps. Accurate file reference verification ensures the navigable knowledge artifacts correctly represent the repository structure and module boundaries.