Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation QA knowledge base. Provides quality checklists, audit criteria, and metrics for documentation review.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Quick reference for documentation quality assessment and audit criteria.
| Dimension | Description | Weight |
|---|---|---|
| Completeness | All APIs/features documented | 25% |
| Accuracy | Code matches documentation | 25% |
| Clarity | Understandable, no jargon | 20% |
| Consistency | Terms, style, format uniform | 15% |
| Navigation | Easy to find information | 10% |
| Freshness | Up-to-date with latest version | 5% |
Score = (Completeness × 0.25) + (Accuracy × 0.25) + (Clarity × 0.20)
+ (Consistency × 0.15) + (Navigation × 0.10) + (Freshness × 0.05)
Rating:
90-100: Excellent
75-89: Good
60-74: Adequate
40-59: Poor
0-39: Critical
| Item | Required | Score |
|---|---|---|
| Project name and description | ✅ | /10 |
| Installation instructions | ✅ | /15 |
| Basic usage example | ✅ | /15 |
| Requirements/dependencies | ✅ | /10 |
| License | ✅ | /5 |
| Badges (build, coverage, version) | ⚪ | /5 |
| Contributing link | ⚪ | /5 |
| Documentation links | ⚪ | /10 |
| Changelog link | ⚪ | /5 |
| Examples work (copy-paste test) | ✅ | /20 |
Total: /100
| Item | Required | Score |
|---|---|---|
| All public classes documented | ✅ | /15 |
| All public methods documented | ✅ | /15 |
| Parameters with types and descriptions | ✅ | /15 |
| Return types documented | ✅ | /10 |
| Exceptions documented | ✅ | /10 |
| Usage examples per endpoint | ✅ | /15 |
| Request/response examples | ⚪ | /10 |
| Error responses documented | ⚪ | /10 |
Total: /100
| Item | Required | Score |
|---|---|---|
| System overview | ✅ | /15 |
| Component descriptions | ✅ | /15 |
| Data flow diagrams | ✅ | /15 |
| Technology stack | ✅ | /10 |
| Decision records (ADRs) | ⚪ | /15 |
| Diagrams render correctly | ✅ | /10 |
| Consistent terminology | ✅ | /10 |
| Cross-references work | ⚪ | /10 |
Total: /100
# Find undocumented public classes
Grep: "^class |^final class |^abstract class " --glob "src/**/*.php"
# Compare with: Grep: "## " --glob "docs/api/**/*.md"
# Find undocumented public methods
Grep: "public function " --glob "src/**/*.php" | wc -l
# Compare with documented count
# Check README sections
Grep: "## Installation|## Usage|## Features" --glob "README.md"
# Find version mismatches
Grep: "version.*[0-9]+\.[0-9]+" --glob "README.md"
# Compare with: Grep: '"version"' --glob "composer.json"
# Find non-existent paths in docs
Grep: "src/[A-Za-z/]+" --glob "docs/**/*.md"
# Verify each path exists
# Find outdated code examples
# Extract code blocks and verify they match current API
# Find undefined acronyms
Grep: "\b[A-Z]{2,}\b" --glob "docs/**/*.md"
# Check for glossary/definition nearby
# Find jargon without explanation
# Manual review of: DDD, CQRS, VO, DTO first usage
# Find walls of text (paragraphs > 5 lines)
# Manual review recommended
# Find broken internal links
Grep: "\]\((?!http)[^\)]+\)" --glob "**/*.md"
# Verify each relative path exists
# Find missing TOC in long docs (> 100 lines)
wc -l docs/**/*.md | awk '$1 > 100 {print $2}'
# Check for: Grep: "## Table of Contents|## Contents" in each
# Find orphan pages (not linked from anywhere)
# Cross-reference all .md files
# Find diagrams with too many elements
Grep: "^\s*[A-Za-z].*\[|^\s*[A-Za-z].*\(" --glob "**/*.md" -A 50
# Count nodes in each mermaid block
# Find diagrams without labels
Grep: "A-->B|1-->2" --glob "**/*.md"
# Should have descriptive IDs
# Find non-rendering mermaid
# Test each ```mermaid block
❌ Missing installation instructions
❌ Broken copy-paste examples
❌ Wrong/outdated code syntax
❌ Missing license
❌ Dead links to key resources
❌ Security-sensitive info in examples
⚠️ Missing API documentation
⚠️ No usage examples
⚠️ Outdated screenshots
⚠️ Inconsistent terminology
⚠️ Missing error handling docs
⚠️ Diagrams don't match code
ℹ️ No badges
ℹ️ Missing contributing guide
ℹ️ No FAQ section
ℹ️ Basic diagrams could be improved
ℹ️ Could add more examples
# Documentation Audit Report
**Project:** {name}
**Date:** {date}
**Auditor:** Claude Code
## Summary
| Metric | Score | Status |
|--------|-------|--------|
| Overall | X/100 | ⚠️ |
| Completeness | X/100 | ✅ |
| Accuracy | X/100 | ❌ |
| Clarity | X/100 | ✅ |
| Consistency | X/100 | ⚠️ |
| Navigation | X/100 | ✅ |
## Critical Issues
### 1. {Issue Title}
- **Location:** {file:line}
- **Problem:** {description}
- **Impact:** {who is affected}
- **Fix:** {recommendation}
## Warnings
### 1. {Issue Title}
- **Location:** {file}
- **Problem:** {description}
- **Recommendation:** {fix}
## Recommendations
1. {Priority action 1}
2. {Priority action 2}
3. {Priority action 3}
## Detailed Findings
### README.md
- [ ] {item}: {status}
### API Documentation
- [ ] {item}: {status}
### Architecture Documentation
- [ ] {item}: {status}
## Next Steps
1. Fix critical issues immediately
2. Address warnings in next sprint
3. Consider recommendations for roadmap
| Action | Impact | Effort |
|---|---|---|
| Fix broken links | High | Low |
| Add missing badges | Medium | Low |
| Add code examples | High | Medium |
| Create README template | High | Medium |
| Add link checker CI | Medium | Low |
| Action | Impact | Effort |
|---|---|---|
| Generate API docs from code | High | High |
| Implement doc-as-code | High | High |
| Create style guide | Medium | Medium |
| Add example testing | High | Medium |
| Diagram automation | Medium | High |
# Example doc validation workflow
documentation:
checks:
- markdown-lint
- link-check
- spelling
- code-example-test
- mermaid-validate
| Tool | Purpose |
|---|---|
| markdownlint | Markdown style |
| markdown-link-check | Broken links |
| alex | Inclusive language |
| mermaid-cli | Diagram validation |
| doctoc | TOC generation |
For detailed information, load these reference files:
references/audit-procedures.md — Step-by-step audit processreferences/scoring-rubrics.md — Detailed scoring criteriareferences/common-issues.md — Frequent documentation problemsreferences/automation.md — CI/CD integration patternsまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
日本語の概要は準備中です。原文の説明を表示しています。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
日本語の概要は準備中です。原文の説明を表示しています。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
日本語の概要は準備中です。原文の説明を表示しています。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
日本語の概要は準備中です。原文の説明を表示しています。