gh:compound-refresh

You can refresh stale pattern docs by validating existing learnings against the current codebase to surface drift, then consolidating affected documentation to reflect updated implementations. It reads configuration to determine language and run mode, outputting a structured report of applied and recommended changes.

Automating knowledge management for docs/solutions involves reviewing learnings against the live codebase and refreshing derived pattern docs. You can enable mode:autofix in your config.local.yaml to automatically apply updates after migrations or major refactors.

Yes, you can automatically fix outdated learnings without manual review by enabling mode:autofix. This mode directly applies updates to derived pattern docs after validating them against the current codebase, bypassing the default interactive mode.

Codebase-alignment validation works by reading existing learnings and pattern docs, comparing them against the live codebase to detect drift, and producing a structured report with Applied and Recommended sections to guide documentation refreshes.

Yes, you need a .compound-engineering/config.local.yaml file at the repo root to run docs-refresh automation. This configuration file determines the language and run mode, allowing you to specify interactive or autofix behavior.

You should avoid autofix mode for maintaining docs/solutions when complex refactors require human judgment, as autofix directly applies changes. Interactive mode is safer, allowing you to review the structured report with Applied and Recommended sections before committing.