Generate per-file documentation with narrative history from commit changes.
npx skills add https://github.com/brsbl/ottonomous --skill doc-brsbl
Please help me install this Agent Skill. Skill: doc Source: https://github.com/brsbl/ottonomous/tree/main/skills/doc Command: npx skills add https://github.com/brsbl/ottonomous --skill doc-brsbl
Captures and preserves the intent, rationale, and context behind code changes by generating per-file documentation and layering narrative around subsequent branches.
Run the doc workflow on your changed files to generate baseline documentation and layer subsequent changes into narrative history.
High-intent search queries and answers about installing and using this skill.
To document code intent, you generate per-file baseline documentation that captures the purpose, decisions, and gotchas for each file. This process preserves the rationale behind code changes by establishing a clear narrative history.
Tracking branch changes is handled by layering narrative updates onto existing baseline documentation. This reflects the evolution of code over time by incrementally updating per-file docs from commit histories across multiple files.
Yes, you can update documentation incrementally from commit histories. The workflow processes subsequent branch changes and layers them into the existing narrative history of the affected files without regenerating the entire baseline.
Yes, per-file documentation supports frontmatter-driven metadata requirements. The generated docs are stored under the .otto/docs/files directory structure to maintain organized knowledge management alongside your codebase.
You need baseline documentation when capturing the initial purpose, decisions, and gotchas of your files. It provides the foundational narrative layer required before tracking subsequent branch changes and code evolution.
A limitation of per-file docs is that the narrative relies on incremental updates from commit histories. If baseline documentation is not established first, tracking subsequent branch changes accurately across multiple files becomes difficult.
VictorHueniAnalyze git diffs to stage files and generate Conventional Commits messages.
zjykzkParse and index Obsidian-flavored Markdown notes with frontmatter, wikilinks, embeds, and callouts.
AlejandroFiginiSave git state, decisions, and remaining tasks to a session snapshot.
channgGenerate static documentation websites from markdown files with sidebar navigation.
