
Doc Writing
Takes a JSON route manifest and turns it into organized markdown API docs by reading your actual source files. Groups routes by their source file, extracts request/response details from the code, and writes one doc per logical group. Outputs a manifest showing what got documented and what didn't. This is meant to sit in a pipeline between route discovery and quality checking, so it's pretty opinionated about structure. If you're already using a route manifest elsewhere in your build, this slots right in. If not, you'll need to generate that JSON first or adjust the input format.
- GitHub stars
- 826
- last updated
- May 30, 2026
Install
$ npx -y skills add huangjia2019/claude-code-engineering --skill doc-writing --agent claude-codeInstalls into .claude/skills of the current project.
Files
Doc Writing Skill
Generate structured API documentation from a route manifest.
Input
You will receive a route manifest (JSON array) from the previous pipeline stage. Each entry contains: method, path, file, line, middleware, type.
Process
Step 1: Read Source Code
For each route in the manifest, read the source file to understand:
- Request parameters (path, query, body)
- Response format
- Error handling
- Business logic summary
Step 2: Generate Documentation
Use the template at templates/endpoint-doc.md for each route group.
Group routes by their source file (e.g., all product routes together).
Step 3: Write Files
Write one markdown file per route group to the docs/ directory:
docs/products-api.mddocs/categories-api.md- etc.
Output
Return a manifest of generated documentation files:
{
"files_generated": ["docs/products-api.md", "docs/categories-api.md"],
"routes_documented": 8,
"routes_skipped": [],
"warnings": []
}
This manifest will be consumed by the next pipeline stage (quality-checking).
Sponsors
Details
- Repository
- github.com/huangjia2019/claude-code-engineering
- Categories
- Backend & APIs, Documentation
- First seen
- Jun 11, 2026