api-documentation
When consumers need to know how to call your API — endpoint docs, OpenAPI specs, request/response examples.
7 skills tagged docs · capability axis.
When consumers need to know how to call your API — endpoint docs, OpenAPI specs, request/response examples.
When users need to know what changed and why — conventional commits parsing, semantic versioning, release notes.
When future-you needs to know why past-you chose this — ADR authoring with context, decision, consequences.
When code needs to explain itself to future readers — JSDoc/docstrings, comment quality, self-documenting patterns.
When your API docs are stale or missing — generates Swagger/OpenAPI YAML from code.
When a new contributor clones the repo and has no idea where to start — creates READMEs with usage and install guides.
When release day shouldn't mean manually writing changelog — parses git logs for changelogs and version bumps.