eo-doc-manager

Initialize, sync, and regenerate eo-doc documentation from source code and git diffs.

30|5|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/SimpleEve/eo-skills --skill eo-doc-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eo-doc-manager
Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-doc-manager
Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-doc-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Repositories often have scattered, stale, or inconsistent documentation that drifts from the codebase and becomes unreliable for developers and AI agents. eo-doc-manager centralizes documentation under eo-doc/, enforces a code-first generation approach, and automates incremental and full rebuilds so docs reflect actual code and recent changes.

Core Features & Use Cases

  • Init: create eo-doc/ directory skeleton, INDEX.md files, templates/ placeholder, and a .sync-cursor baseline.
  • Sync (incremental): drive doc changes from git diff to update doc/, agent-handbook/, design/ impl status, and all INDEX.md entries.
  • Re-sync (full rebuild): scan source code to regenerate doc/ and agent-handbook/, preserve human-authored design/research content, and reset the sync baseline.
  • Modify / Select / Query: parse and route natural-language or explicit commands to create, split, and search documents by tags and keywords.
  • Governance: manage CLAUDE.md injection, frontmatter validation, impl_coverage tracking, and consistency checks between design/doc/agent-handbook.

Quick Start

Use the eo-doc-manager skill to sync documentation for the latest commit range and update eo-doc/INDEX.md.

Frequently Asked Questions about eo-doc-manager

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

FAQPage Schema
How do I sync project documentation with git diff?

To sync project documentation with git diff, you perform an incremental update driven by recent commits, refreshing doc/, agent-handbook/, design status, and INDEX.md entries to match source code changes.

What is a code-first documentation workflow?

A code-first documentation workflow generates and updates documentation directly from source code and git diffs, ensuring that project docs never drift from the actual implementation and remain reliable for agents.

How do I initialize a documentation directory skeleton?

To initialize a documentation directory skeleton, you create the eo-doc/ structure, populate INDEX.md files, set up templates/ placeholders, and establish a .sync-cursor baseline for tracking future updates.

Can I regenerate agent-handbook from source code without losing human-authored design docs?

Yes, you can regenerate agent-handbook from source code without losing human-authored content. A full re-sync scans source to rebuild docs while preserving existing design and research files.

Why does documentation drift from the codebase?

Documentation drifts from the codebase when updates are manual and scattered across files. Without automated incremental or full rebuilds, project docs become stale and unreliable for developers.

What is the best way to manage CLAUDE.md injection and frontmatter validation?

The best way to manage CLAUDE.md injection and frontmatter validation is using a governance workflow that enforces consistency checks across design, doc, and agent-handbook during sync operations.