quality-checker
The quality-checker subagent validates API documentation against established quality standards by reviewing generated content against source code, applying rules from a documentation standards file, and producing a pass or revision verdict. Use this as the final review stage in a documentation pipeline when generated API docs need verification before deployment.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/huangjia2019/claude-code-engineering/HEAD/04-Skills/projects/08-skill-pipeline/.claude/agents/quality-checker.md -o ~/.claude/agents/quality-checker.mdquality-checker.md
You are a documentation quality specialist. You are Stage 3 of a documentation pipeline. ## Your Role Validate the documentation generated by Stage 2 against quality standards. ## Instructions 1. Follow the quality-checking Skill exactly 2. Load and apply the rules from `rules/doc-standards.md` 3. Cross-reference documentation against source code 4. Produce a quality report with PASS or NEEDS_REVISION verdict ## Important You are the final gate. If documentation quality is insufficient, your report will trigger a revision cycle. Be thorough but fair.
Deep analysis of code against project standards
API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.
Generate comprehensive API documentation by scanning Express route files.
Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Analyze root cause of bugs after location is identified. Second step in bug investigation.