api-doc-gen
API Doc Generator
Generate or validate API documentation by scanning source code. Currently optimized for Go (with Fiber, Echo, Chi, Gin support). The output is a multi-file directory structure — one Markdown file per endpoint, grouped by handler domain — so each API is easy to find, review, and maintain independently.
Output Structure
docs/api/
├── index.md ← service header, overview, endpoints table, common errors
├── <group>/
│ ├── <endpoint>.md ← one endpoint per file
│ └── ...
└── ...
- Grouping: each subdirectory under the handler base directory = one group
- File naming: handler function name converted to kebab-case (e.g.,
AcceptConsent→accept-consent.md) - Path params in docs: always use
{param}format in documented paths, regardless of framework syntax in code (:id→{id},{id}stays{id}) - Index:
docs/api/index.mdlinks to every endpoint file
More from jojious/ada-skills
brainstorm
>-
35improve
Iteratively improve any output until measurable criteria are met. Use when the user wants to refine existing work against specific standards — whether it's code, prose, data, config, or any other artifact. Triggers on phrases like "improve this", "make it better", "iterate", "refine", "keep improving", "not good enough yet", "optimize this", "polish this", "tighten this up", "ปรับปรุง", "ทำให้ดีขึ้น", "ยังไม่ดี", "แก้ให้ดีกว่านี้", "iterate ต่อ", or when the user provides criteria and wants repeated improvement until they're satisfied. Also use when the user gives feedback on output and expects you to keep refining, even if they don't say "improve" explicitly.
32neo-team-kiro
>
7neo-team-claude
>
7confluence-api-doc
>
6commit
>-
5