docs skill
The Afterburner challenge got me thinking: what’s a skill that would be useful across any repo?
Generate-documentation is a GitHub Copilot skill that analyzes a codebase and produces a full docs site. It follows a 5-step workflow: map the territory, identify key components, generate documentation, configure mkdocs, and run quality checks. Output is a browsable docs/ directory with an mkdocs.yml.
The interesting design choice: when existing docs are present, it fills gaps without touching what’s already there. No overwrites, no merge conflicts. It respects human-written content and only adds what’s missing.
Tested against 5 repos of different sizes and types. Token usage scales with repo complexity, not repo size.
Thanks for reading! :-)