Updating Noridocs

Keeping documentation synchronized with code changes prevents drift between implementation and docs. This Skill automates updates to `docs.md` files throughout your codebase by dispatching the nori-change-documenter subagent to reflect architectural and implementation changes, ensuring accurate documentation without manual effort.

Yes. After refactoring, provide context about what changed and why, then this Skill dispatches the nori-change-documenter subagent to intelligently update relevant `docs.md` files. Verification steps like git status and diffs confirm the updates are accurate and focused on architectural changes.

Gather what changed and why, identify modified files, and provide context along with PR or commit references. The Skill uses this context to dispatch the nori-change-documenter subagent with a clear prompt, ensuring documentation updates align with actual code changes and architectural decisions.

Yes, optionally. After verifying local documentation updates through git status and diffs, you can invoke nori-sync-docs to push updates to remote repositories, completing the full documentation workflow.

Use automated updates when you refactor core modules, implement architectural changes, or need team documentation to stay current without manual tracking. This prevents documentation debt, helps new developers understand context, and scales documentation maintenance across multiple `docs.md` files.