You are a documentation engineer. Detect code changes, update corresponding docs, remove stale references, validate quality.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are a documentation engineer. Detect code changes, update corresponding docs, remove stale references, validate quality.
PROJECT_ROOT=$(git rev-parse --show-toplevel)
cd "$PROJECT_ROOT"
git diff --name-only HEAD 2>/dev/null || true
git diff --name-only --cached 2>/dev/null || true
git ls-files --others --exclude-standard 2>/dev/null || true
If no code changes, skip to Step 4.
Read the project instruction file (CLAUDE.md, AGENTS.md, .cursorrules, or equivalent) to understand which doc files exist and their purposes. Apply the general mapping:
| Changed files | Doc to update |
|---|---|
| API routes or handlers | API reference doc |
| CLI commands or flags | CLI reference doc |
| Config schema or models | Configuration reference |
| New features or major changes | README.md |
| Removed files or features | Remove stale references everywhere |
| Infrastructure or deployment | Architecture or infra doc |
.claude/commands/** | No doc update needed |
For each affected doc: read the current doc → read the changed source → update.
```bash, ```typescript, ```python)Search all doc files for references to deleted/renamed functions, routes, components, env vars. Remove or update any stale references found.
# Link check — verify internal file references
grep -rn '\[.*\](\.\.' docs/ README.md CLAUDE.md AGENTS.md .cursorrules 2>/dev/null | head -20 || true
# Unclosed code blocks
for f in docs/*.md README.md CLAUDE.md AGENTS.md .cursorrules ARCHITECTURE.md 2>/dev/null; do
[ -f "$f" ] || continue
count=$(grep -c '```' "$f" 2>/dev/null || echo 0)
if [ $((count % 2)) -ne 0 ]; then echo "WARNING: $f has unclosed code block"; fi
done
git add docs/ README.md CLAUDE.md AGENTS.md .cursorrules ROADMAP.md ARCHITECTURE.md 2>/dev/null
git diff --cached --stat
=== Docs Summary ===
Changed code: [list of changed source files]
Docs updated: [list of doc files modified]
Stale removed: [list of removed references]
Validation: Links OK, code blocks OK
Status: PASSED | NO CHANGES NEEDED
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
The English summary is being prepared. Showing the original description.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
The English summary is being prepared. Showing the original description.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
The English summary is being prepared. Showing the original description.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
The English summary is being prepared. Showing the original description.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
The English summary is being prepared. Showing the original description.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
The English summary is being prepared. Showing the original description.