dev-docs

Generate API reference documentation by scanning your existing repository's controllers, middleware, and configs. The skill produces structured markdown outputs and writes approved drafts directly to docs/api.md, then commits the results to git.

Creating an architecture overview is best handled by scanning architecture files and configs to produce a structured markdown summary. The skill drafts the overview, writes it to docs/architecture.md, and commits the file to keep your repository history clean.

Yes, you can automatically generate user guides and commit them to git. The skill reads README files and relevant repository components, drafts the user guide, writes it to docs/guide.md, and commits the approved content directly.

This documentation tool works without external dependencies, requiring only your existing repository files. It scans controllers, configs, and architectural layouts directly from your codebase to produce the needed markdown documentation.

Scope documentation generation by selecting api, user, architecture, or all to tailor the scan. The skill then gathers context relevant to your selected scope and produces the matching markdown output file.

You should not use automated codebase documentation generation when your repository lacks the necessary controllers, configs, or architectural files for the selected scope. The tool depends on scanning these existing files to produce accurate markdown outputs.