Generate and reconstruct project documentation from source code with evidence tracking.
npx skills add https://github.com/haposoft/cafekit --skill hapo-docs
Please help me install this Agent Skill. Skill: hapo:docs Source: https://github.com/haposoft/cafekit/tree/main/packages/spec/src/claude/skills/docs Command: npx skills add https://github.com/haposoft/cafekit --skill hapo-docs
This Skill solves the problem of inadequate or missing documentation by generating and reconstructing project/system documentation directly from source code, including evidence and uncertainty tracking.
Invoke the hapo:docs skill to create documentation for your project.
High-intent search queries and answers about installing and using this skill.
You can reconstruct missing documentation from source code by generating architectural overviews and requirement summaries. This process uses evidence tracking to ensure accuracy and manage uncertainties when documenting legacy systems.
Evidence tracking in documentation reconstruction links generated summaries and architectural overviews directly to source code. It ensures accuracy and manages uncertainties by validating reconstructed requirements against actual codebase evidence.
Yes, you can automate the creation, update, and summarization of project documentation directly from a codebase. This handles both new and legacy systems by summarizing codebases and reconstructing requirements as they evolve.
Yes, source code documentation generation can work without external dependencies. The process uses internal scripts, references, and assets to summarize codebases and reconstruct architectural overviews with evidence tracking.
The best way to document legacy systems with missing requirements is to reconstruct as-is documentation directly from the source code. This approach uses evidence tracking to maintain accuracy and manage uncertainties during reconstruction.
You should use evidence tracking for system documentation when reconstructing requirements or architectural overviews from source code, especially for legacy systems. It ensures accuracy and manages uncertainties when original documentation is missing.
hidonguyenAnalyze codebases and generate structured documentation in the docs/ directory.
rloisellGenerate and export architectural diagrams in draw.io, PlantUML, and Mermaid formats.
philo-grovesConstruct static analysis graphs for reachability, guard dominance, and path feasibility.
hypeJunctionProvides guidelines for writing code comments, JSDoc, and interface documentation.
