Deck Context Doc Maintainer

3. Gather hard evidence before edits:

• Use manifests and package metadata as source of truth.
• Use exact file paths and command output snippets.
• Prefer rg and find over manual scanning.

4. Apply minimal, high-signal edits:

• Keep docs in English.
• Preserve existing style and relative links.
• Update only inconsistent claims; avoid broad rewrites.
• Make historical boundaries explicit where needed.

5. Re-validate:

node scripts/check_docs_entry.mjs

6. Report outcomes with:

• Findings list (severity + file + rationale).
• Files updated.
• Validation results.
• Residual risks or deferred follow-ups.

Decision Rules

• Treat repo config and code as canonical over prose docs.
• Treat generated surfaces as generated unless explicit override exists.
• If a doc statement cannot be proven from repo evidence, rephrase or remove it.
• Keep differences between shared guide vs app-specific guide explicit.
• Do not edit unrelated product or implementation code during doc alignment work.

Quick Commands

# Baseline context audit
bash skills/deck-context-doc-maintainer/scripts/audit-context.sh

# Link and module matrix validation
node scripts/check_docs_entry.mjs

# Quick workspace truth check
sed -n '1,120p' pnpm-workspace.yaml
sed -n '1,120p' go.work
sed -n '1,120p' pyproject.toml

References

• Detailed checklist: references/review-checklist.md
• Audit helper: scripts/audit-context.sh

Use the checklist when generating review findings or implementation plans for doc alignment.