Use this skill for general documentation updates with built-in quality gates. Use when updating documentation after code changes, enforcing writing guidelines, maintaining ADRs. Do not use when README-specific updates - use update-readme instead. DO NOT use when: complex multi-file consolidation - use doc-consolidation.
Updates documentation files with quality gates, style enforcement, and accuracy verification after code changes.
/plugin marketplace add athola/claude-night-market/plugin install pensive@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/accuracy-scanning.mdmodules/adr-patterns.mdmodules/capabilities-sync.mdmodules/consolidation-integration.mdmodules/directory-style-rules.mdUse this skill when code changes require updates to the README, plans, wikis, or docstrings. Run Skill(sanctum:git-workspace-review) first to capture the change context.
The documentation update workflow includes several specialized functions. It identifies redundancy through consolidation detection and enforces directory-specific style rules, with strict limits for docs/ and more lenient ones for the book/ directory. The system also verifies the accuracy of version numbers and component counts and integrates with the LSP for semantic documentation verification in supported versions of Claude Code.
doc-updates:context-collected - Git context + CHANGELOG reviewdoc-updates:targets-identifieddoc-updates:consolidation-checked (skippable)doc-updates:edits-applieddoc-updates:guidelines-verifieddoc-updates:slop-scanned - AI marker detection via scribedoc-updates:plugins-synced - plugin.json ↔ disk auditdoc-updates:capabilities-synced - plugin.json ↔ documentation syncdoc-updates:accuracy-verifieddoc-updates:previewcontext-collected)Skill(sanctum:git-workspace-review) has been run.CHANGELOG Reference (critical for version sync):
# Check recent CHANGELOG entries for undocumented features
head -100 CHANGELOG.md
# Compare documented version vs plugin versions
grep -E "^\[.*\]" CHANGELOG.md | head -3
for p in plugins/*/.claude-plugin/plugin.json; do
jq -r '"\(.name): \(.version)"' "$p"
done | head -5
Cross-reference CHANGELOG entries against:
book/src/reference/capabilities-reference.md - All skills/commands/agentsbook/src/plugins/ - Per-plugin docstargets-identified)docs/ - Reference documentation (strict style)book/ - Technical book content (lenient style)README.md files at project and plugin rootswiki/ entries if presentwiki/architecture/ (or wherever ADRs are located).consolidation-checked)Load: @modules/consolidation-integration.md
Purpose: Detect redundancy and bloat before making edits.
Scan for:
User approval required before:
Skip options:
--skip-consolidation flag to bypass this phaseExit criteria: User has approved/skipped all consolidation opportunities.
edits-applied)modules/adr-patterns.md for complete template structure, status flow, immutability rules, and best practices.guidelines-verified)Load: @modules/directory-style-rules.md
Maintain consistent documentation by applying directory-specific rules. The system checks for and removes filler phrases such as "in order to" or "it should be noted" and ensures that no emojis are present in the body text of technical documents. Use grounded language with specific references rather than vague claims, and maintain an imperative mood for instructions. For lists of three or more items, prefer bullets over prose to improve scannability.
The audit will issue warnings for paragraphs that exceed length limits or files that surpass the established line count thresholds. We also flag marketing language and abstract adjectives like "capable" or "smooth" to maintain a technical and direct tone across all project documentation.
slop-scanned)Run Skill(scribe:slop-detector) on edited documentation to detect AI-generated content markers.
The scribe plugin provides comprehensive AI slop detection:
Skill(scribe:slop-detector) --target [edited-files]
This detects:
For enhanced writing quality, check for elements-of-style:writing-clearly-and-concisely:
# If superpowers/elements-of-style is installed:
Skill(elements-of-style:writing-clearly-and-concisely)
# Fallback if not installed - use scribe:doc-generator principles:
Skill(scribe:doc-generator) --remediate
The fallback provides equivalent guidance:
If slop score exceeds 2.5 (moderate), run:
Agent(scribe:doc-editor) --target [file]
This provides interactive section-by-section cleanup with user approval.
--skip-slop flag to bypass slop detectionplugins-synced)Audit plugin.json files against disk (prevents registration drift):
# Quick discrepancy check for all plugins
for plugin in plugins/*/; do
name=$(basename "$plugin")
pjson="$plugin/.claude-plugin/plugin.json"
[ -f "$pjson" ] || continue
# Count commands
json_cmds=$(jq -r '.commands | length' "$pjson" 2>/dev/null || echo 0)
disk_cmds=$(ls "$plugin/commands/"*.md 2>/dev/null | wc -l)
# Count skills (directories only)
json_skills=$(jq -r '.skills | length' "$pjson" 2>/dev/null || echo 0)
disk_skills=$(ls -d "$plugin/skills"/*/ 2>/dev/null | wc -l)
# Report mismatches
if [ "$json_cmds" != "$disk_cmds" ] || [ "$json_skills" != "$disk_skills" ]; then
echo "$name: commands=$json_cmds/$disk_cmds skills=$json_skills/$disk_skills"
fi
done
If mismatches found: Run /update-plugins --fix or manually update plugin.json files.
Why this matters: Unregistered commands/skills won't appear in Claude Code's slash command menu or be discoverable.
capabilities-synced)Load: @modules/capabilities-sync.md
Purpose: Ensure plugin.json registrations are reflected in reference documentation.
Sync Targets:
| Source | Documentation Target |
|---|---|
plugin.json.skills[] | book/src/reference/capabilities-reference.md |
plugin.json.commands[] | book/src/reference/capabilities-reference.md |
plugin.json.agents[] | book/src/reference/capabilities-reference.md |
hooks/hooks.json | book/src/reference/capabilities-reference.md |
| Plugin existence | book/src/plugins/{plugin}.md |
Quick Check:
# Compare registered vs documented skills
for pjson in plugins/*/.claude-plugin/plugin.json; do
plugin=$(basename $(dirname $(dirname "$pjson")))
jq -r --arg p "$plugin" '.skills[]? | sub("^\\./skills/"; "") | "\($p):\(.)"' "$pjson" 2>/dev/null
done | sort > /tmp/registered-skills.txt
grep -E "^\| \`[a-z-]+\` \|" book/src/reference/capabilities-reference.md | \
head -120 | awk -F'|' '{print $2":"$3}' | sort > /tmp/documented-skills.txt
# Show missing
comm -23 /tmp/registered-skills.txt /tmp/documented-skills.txt
If discrepancies found:
book/src/plugins/{plugin}.mdbook/src/SUMMARY.mdAuto-generate entry format:
| `{skill-name}` | [{plugin}](../plugins/{plugin}.md) | {description} |
Skip options: Use --skip-capabilities to bypass this phase.
accuracy-verified)Load: @modules/accuracy-scanning.md
Validate claims against codebase:
# Quick version check
for p in plugins/*/.claude-plugin/plugin.json; do
jq -r '"\(.name): \(.version)"' "$p"
done
# Quick counts
echo "Plugins: $(ls -d plugins/*/.claude-plugin/plugin.json | wc -l)"
echo "Skills: $(find plugins/*/skills -name 'SKILL.md' | wc -l)"
Verification: Run the command with --help flag to verify availability.
Flag mismatches:
LSP-Enhanced Verification (2.0.74+):
When ENABLE_LSP_TOOL=1 is set, enhance accuracy verification with semantic analysis:
API Documentation Coverage:
Signature Verification:
Reference Finding:
Code Structure Validation:
Efficiency: LSP queries (50ms) vs. manual file tracing (minutes) - dramatically faster verification.
Default Strategy: Documentation updates should prefer LSP for all verification tasks. Enable ENABLE_LSP_TOOL=1 permanently for best results.
Non-blocking: Warnings are informational; user decides whether to fix.
preview)git diff <file> or rg snippets).TodoWrite items are completed and documentation is updated.wiki/architecture/ (or the established ADR directory) with the correct status and links to related work.| Flag | Effect |
|---|---|
--skip-consolidation | Skip Phase 2.5 consolidation check |
--skip-slop | Skip Phase 4.25 AI slop detection |
--strict | Treat all warnings as errors |
--book-style | Apply book/ rules to all files |
Documentation out of sync
Run make docs-update to regenerate from code
Build failures Check that all required dependencies are installed
Links broken Verify relative paths in documentation files
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.