メニュー
This skill should be used when the user asks to "classify docs", "what documentation do I need", "analyze doc needs", "documentation audit", or needs to determine what documentation types are needed based on code changes. Analyzes git commits and feature scope to return structured classification data.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | doc-classifier |
| description | This skill should be used when the user asks to "classify docs", "what documentation do I need", "analyze doc needs", "documentation audit", or needs to determine what documentation types are needed based on code changes. Analyzes git commits and feature scope to return structured classification data. |
Classify documentation needs based on code changes.
Analyzes git commits, file changes, and feature scope to determine what documentation types are needed. Returns structured classification data.
| Input | Type | Description |
|---|---|---|
feature_name | string | Optional feature name to analyze |
commit_range | string | Git commit range (default: HEAD~10) |
format | string | Output format: json, summary, actions |
{
"feature": "session tracking",
"scope": {
"commands": ["sessions live", "sessions current", "sessions task"],
"modules": ["src/aiterm/sessions/"],
"hooks": ["session-register", "session-cleanup"],
"files_changed": 23,
"commits": 15
},
"classification": {
"guide": { "score": 8, "needed": true, "reason": "New module with 5 CLI commands" },
"refcard": { "score": 5, "needed": true, "reason": "5 new commands" },
"gif_demo": { "score": 6, "needed": true, "reason": "User-facing CLI workflow" },
"mermaid": { "score": 7, "needed": true, "reason": "Hook-based event system" }
}
}
| Factor | Guide | Refcard | GIF | Mermaid |
|---|---|---|---|---|
| New command (each) | +1 | +1 | +0.5 | +0 |
| New module | +3 | +1 | +1 | +2 |
| New hook | +2 | +1 | +1 | +3 |
| Multi-step workflow | +2 | +0 | +3 | +2 |
| Config changes | +0 | +2 | +0 | +0 |
| Architecture change | +1 | +0 | +0 | +3 |
| User-facing CLI | +1 | +1 | +2 | +0 |
# Find new @app.command decorators
git diff HEAD~10 --name-only | xargs grep -l "@app.command"
# Parse command names
grep -E "@app\.command\(|def \w+\(" src/*/cli/*.py
# New directories with __init__.py
git diff --diff-filter=A HEAD~10 --name-only | grep "__init__.py"
# Hook-related files
git diff HEAD~10 --name-only | grep -E "hook|event"
# Hook configuration
grep -E "SessionStart|Stop|PreToolUse" ~/.claude/settings.json
# Subcommand groups (Typer)
grep "typer.Typer()" src/*/cli/*.py
# Multi-step docs
grep -E "Step [0-9]" docs/**/*.md
# Internal call
classification = doc_classifier(
feature_name="session tracking",
commit_range="HEAD~15"
)
if classification["guide"]["needed"]:
# Generate guide
pass
/skill doc-classifier "session tracking" --format json
Used by:
/craft:docs:analyze - Main classification command/folio:docs:guide - Determine what to generate/craft:docs:feature - Smart detection enhancement/craft:docs:update - Selective updatesComplements:
mermaid-linter skill - Validate generated diagramschangelog-automation skill - Detect feature boundariesThis skill should be used when the user asks to "create a demo", "build a code demonstration", "write a vignette", "generate tutorial code", "make live-coding examples", "demo this package", or wants runnable instructional code for teaching, presentations, vignettes, or documentation. Designs progressive code examples that build from simple to complex with explanations, expected outputs, and common variations.
This skill should be used when the user asks to "validate Mermaid diagrams", "lint diagrams", "check diagram syntax", "mermaid health score", or needs to validate Mermaid diagrams in markdown files for syntax errors, configuration, and rendering quality. Uses mcp-mermaid for full validation and local regex for fast pre-checks.
This skill should be used when the user asks to "update nav", "sync mkdocs navigation", "add a doc page", "reorganize navigation", "fix orphan docs", or needs to keep mkdocs.yml in sync with the docs/ directory. Handles directory-driven nav updates, new-page scaffolding with auto-nav insertion, and ADHD-friendly nav reorganization (≤7 top-level sections, ≤3 nesting depth).
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
This skill should be used when the user asks to "set up a docs site", "build the site", "preview docs locally", "deploy docs", "publish the site", "audit site content", "change site theme", "check site health", "show site status", or otherwise manages the lifecycle of a documentation site (MkDocs, Quarto, pkgdown). Covers init/create/theme through build/preview/audit through deploy/publish/update.