Nexu Documentation Sync
Review code changes and update project documentation for consistency.
Mode
| Mode | How to activate | Behavior |
|---|---|---|
delta (default) |
No argument, or say "delta" | Diff against merge-base with origin/main + working tree changes |
full |
Say "full audit" or "full sync" | Complete audit of all docs against current codebase |
| Scope keyword | Say the keyword (e.g. "db", "api") | Targeted check (see Scope Filters below) |
Delta Mode Baseline
Identify changed files using merge-base (not a fixed commit count):
# Branch changes since diverging from main
git diff --name-only $(git merge-base HEAD origin/main)...HEAD
# Plus staged + unstaged
git diff --name-only --cached
git diff --name-only
Combine the results into a single list of changed files. Then use the Impact Mapping to identify which docs may need updates.
Impact Mapping
Map changed areas to the docs they affect:
| Changed area | Affected docs |
|---|---|
apps/controller/src/routes/ |
specs/references/api-patterns.md, ARCHITECTURE.md, specs/product-specs/*.md (if route is user-facing) |
apps/web/src/pages/ or apps/web/src/app.tsx |
specs/FRONTEND.md |
apps/landing/ |
ARCHITECTURE.md (Monorepo layout) |
apps/controller/src/runtime/ |
ARCHITECTURE.md, specs/RELIABILITY.md |
packages/shared/src/schemas/ |
ARCHITECTURE.md (Type safety) |
package.json scripts |
CLAUDE.md + AGENTS.md Commands sections |
| New apps/packages dirs | ARCHITECTURE.md (Monorepo layout) |
| Config generator | specs/references/openclaw-config-schema.md, specs/openclaw-config-reference.md |
| Auth changes | specs/SECURITY.md |
| New/moved doc files | CLAUDE.md Doc Map, AGENTS.md Where to look, relevant index files |
Cross-Reference Pairs
Always verify consistency between these paired docs:
CLAUDE.mdCommands section <->AGENTS.mdCommands section (same entries)CLAUDE.mdDocumentation Map paths <-> actual files on diskCLAUDE.mdHard Rules <->AGENTS.mdHard rulesARCHITECTURE.mdmonorepo layout <-> actualapps/+packages/dirsspecs/DESIGN.mdtable <-> actualspecs/design-specs/+specs/designs/contentsspecs/design-specs/index.mdtable <-> actual design filesspecs/product-specs/index.mdtable <-> actualspecs/product-specs/*.mdfilesspecs/PLANS.mdtable <->specs/exec-plans/{active,completed}/contentsspecs/FRONTEND.mdPages table <->apps/web/src/app.tsxroutes
Scope Filters
When the user specifies a scope keyword, limit the check to that area:
| Keyword | What it checks |
|---|---|
db |
Schema source vs specs/generated/db-schema.md |
api |
Route files vs specs/references/api-patterns.md |
frontend |
apps/web/ vs specs/FRONTEND.md |
commands |
package.json scripts vs CLAUDE.md/AGENTS.md Commands sections |
architecture |
All apps/ + packages/ vs ARCHITECTURE.md layout |
security |
Auth/crypto code vs specs/SECURITY.md |
links |
Verify all doc map paths and index references resolve to existing files |
guides |
specs/guides/** internal cross-references |
designs |
specs/designs/** + specs/design-specs/** vs index files |
exec-plans |
specs/exec-plans/** vs specs/PLANS.md |
product-specs |
specs/product-specs/** vs index + specs/PRODUCT_SENSE.md |
Rules
- Never remove forward-looking documentation — ask if uncertain whether content is aspirational or stale.
- Preserve original language (English/Chinese) and writing style of existing docs.
- For backend API updates, treat
apps/controlleras the source of truth; do not reference removed legacy package paths. - Always verify
CLAUDE.md<->AGENTS.mdconsistency after any update to either file. - Do NOT auto-commit — present the diff summary and let the user decide when to commit.
Workflow
- Determine mode from user request (default: delta).
- If delta mode: run the git diff commands above, collect changed files.
- Map changed files to affected docs using the Impact Mapping.
- Read each affected doc and compare against current code.
- Check all Cross-Reference Pairs for consistency.
- Present findings: what's outdated, what's missing, what's inconsistent.
- Apply fixes with user approval.
- After fixes, re-verify Cross-Reference Pairs touched by changes.