What problem does it solve? Architecture and domain documentation drifts out of sync with code as repositories evolve, forcing agents and developers to re-derive system knowledge from scratch. This Skill audits the docs/resources knowledge base against actual code, task history, and git changes, updating only the docs that evidence shows are stale. ## Core Features & Use Cases - Drift Detection: Builds a candidate change set from git diffs, commit logs since last review dates, and task completion harvests, then maps changed files to registered areas and components. - Evidence-Based Updates: Edits area summaries, dependency graphs, feature contracts, runbooks, and component CONTEXT.md files only when code, tests, or task history prove them stale. - External Storage Support: Redirects writes to a central docs root via the CONTEXT_DOCS_DIR environment variable for cross-repo knowledge bases. - Use Case: After merging a feature that changed a service's public interface, ask the agent to refresh context so the component CONTEXT.md, area dependency graph, and glossary reflect the new reality. ## Quick Start Ask the agent to refresh context and check for documentation drift after the recent code changes.
