workflow-docs-review

Documentation updates are applied as minimal, idempotent diffs grounded in the Project Context Cache, avoiding large rewrites and preventing drift between docs and code. It edits existing files only without restructuring or adding unrelated sections.

Yes, focused documentation scanning supports configurable filters for user, dev, feature, release, or all areas. You can also set an optional scope path to limit scanning to targeted repository directories.

PR integration respects the git.pr_mode setting (off, optional, required) and will skip or prompt for pull requests accordingly. After applying doc changes, it finalizes by updating bootstrap state and syncing the cache.

PCC grounding refreshes the Project Context Cache before inspecting repository state and syncs it after documentation changes using the appropriate scope. This ensures docs reflect current project facts with minimal disruptive edits.

Run the review workflow with focus set to all and scope set to the repository root to refresh PCC, apply minimal doc updates, sync PCC, and optionally open a pull request in one pass.

This approach never restructures existing documents or adds unrelated sections, applying only minimal idempotent edits. Large documentation overhauls or new document creation fall outside its scope.