context-update

To update shared context files when your tech stack changes, this Skill reads the current state, compares it with recent decisions, and generates diffs for human review before applying commits. It ensures your central context stays accurate and prevents drift across repositories.

Keeping architecture documentation fresh after adding a new repository involves reading current context files like repos.yaml and architecture.md, generating a diff of proposed updates, and committing the approved changes. This proactive approach prevents central context drift across your docs and decisions.

Yes, you can generate diffs for human review when team composition updates happen. The Skill reads relevant context files, detects changes in team composition or quarterly OKRs, and proposes updates for your approval before applying commits to the central context.

Preventing context drift across multiple repositories requires proactively detecting architecture, team, or tech stack changes and proposing updates to central context files. This Skill reads the current state, generates review diffs, and supports human approval workflows to apply commits with clear messages.

Yes, this context update workflow requires manual commit approval. It generates a review diff of proposed updates to files like tech-stack.md and repos.yaml, waits for your approval, and then applies the commits with clear messages to ensure collaborative context management.