Doc Update

Use the user's targets. Without explicit targets, inspect root guidance and README files, then follow documentation affected by the current changes. Do not expand a narrow correction into a full documentation audit.

Verify material claims against code, configuration, generated help, or policy. Account for staged and unstaged changes. Keep commands, paths, and terminology consistent. Put detailed guidance in one canonical location and link to it where readers need it.

For skill documentation, make triggers specific and load references only for the relevant task. Preserve concrete safeguards and remove generic instructions that do not change decisions.

Validate changed links, commands, and instructions with checks suited to the change. Run commands only when their effects are authorized. Explain any unverified claim or blocked check instead of presenting it as confirmed.

For a broad audit, use the audit checklist. Finish when the requested documents reflect repository truth and their affected references agree. Report changes, validation, and unresolved mismatches.