Code Docs provides practical, repo-adjacent guidance and templates for generating and maintaining documentation across languages and project types. It consolidates best practices for README structure, API documentation (TypeDoc, Sphinx, godoc), changelog conventions (Keep a Changelog), and architecture docs so engineers can quickly produce consistent, testable documentation. The skill includes command examples for TypeScript, Python, and Go and prescribes a simple workflow: identify documentation needs, generate or update docs, verify examples and links, then commit with a clear message.
Use this skill when adding new features, changing public APIs, preparing releases, or when a contributor asks "how do I document this?" Ideal for repository maintainers who want reproducible docs generation (TypeDoc, Sphinx, mkdocs) and a minimal README template for project onboarding.
Best used by developer-focused agents with shell and file access that can run language toolchains (Node, Python, Go) or invoke repository build steps.
A documentation-generation skill that provides templates and commands for README, API docs, changelogs, and architecture docs across TypeScript, Python, and Go. The SKILL.md is a reasonable reference but acts more as a static cheat sheet than an actionable agent workflow — it lists generation commands but lacks decision logic for when/how to invoke them. No scripts bundled, so everything must be executed manually by the agent. References/ directory is mentioned but not included in the fetched data.
Clean skill with no security concerns. No credentials, no network calls, no destructive commands. The main weakness is that it's essentially a well-organized markdown reference rather than a skill with automation scripts. Could be much more useful with bundled templates or a generation script.