Update developer docs from code changes in Claude Code

Reconcile module exports, directories, and usage across root and module documentation without duplicating details.

Install in Claude Code

A Claude Code workspace and its development docs. Provide the module scope or start a full documentation audit without arguments.

Review `.claude/skills/dev-doc/SKILL.md` and its requirements at the pinned GitHub commit.
Create `.claude/skills/dev-doc/` in your project and save the reviewed file as `.claude/skills/dev-doc/SKILL.md`.
Start Claude Code from that project's root, then select `/dev-doc` in the slash menu.

Example task

The preview module renamed draftPreview to reportPreview. Source facts are `{module:'preview',old:'draftPreview',current:'reportPreview'}`. The root guide describes module responsibilities, while its README still shows the old name.

What to check

Update the module README to `export=reportPreview`. Keep the module responsibility in the root guide, check its name and directory, and leave other interfaces as recorded.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

Which documentation should change after a module update?

Compare the current source and both levels of docs. Keep responsibilities in the root guide and exports or usage in the module README. Verify the documented paths and names.