forge-keeper

You can keep CLAUDE.md files synchronized by invoking a keeper subagent that generates structured proposals to align root and child files. It coordinates updates across rules and exemplars, returning proposals for human confirmation before applying changes.

Project documentation drifts when rules and exemplars evolve without a synchronization mechanism. A keeper subagent prevents this by capturing proposed updates before context-clearing actions like /compact or /clear, ensuring structured proposals keep artifacts aligned.

The best way to maintain CLAUDE.md consistency before /compact is to run a synchronization workflow that captures proposals for documentation updates. This subagent runs alongside your session to safely preserve context and align root and child files.

Yes, you can use a keeper subagent that operates as a teammate to avoid polluting your main context window. It processes references and rules independently, returning only the structured proposal for your review.

Yes, the CLAUDE.md sync process requires human confirmation before applying updates. It relies on structured proposal formats and references to suggest changes, ensuring you maintain control over what modifications are applied to the repository.

You should avoid automated CLAUDE.md maintenance when you need immediate, unreviewed file mutations. This approach enforces structured proposals and human confirmation, meaning it is designed for deliberate synchronization rather than rapid, unchecked edits.