← ClaudeAtlas

context-maintainerlisted

Maintain accurate module and page documentation under .agents/context after repository changes. Use after code, configuration, UI, API, role, test, or architecture changes; when auditing stale context; when adding a module or page; and when recording major behavioral changes in the standard context format.
omergocmen/CrewCtl · ★ 43 · AI & Automation · score 74
Install: claude install-skill omergocmen/CrewCtl
# Context Maintainer Keep `.agents/context` aligned with the current repository without turning it into a raw changelog. ## Workflow 1. Read `.agents/context/index.md`. Map each source changed in the current task to its owning context files. 2. Distinguish files changed in the current task from unrelated pre-existing working-tree changes. Never document an unrelated dirty file as work completed by the current task. 3. Read the changed source and its existing context. Update current-state documentation when responsibilities, behavior, inputs, outputs, contracts, dependencies, configuration, user flows, risks, or verification paths changed. 4. Correct incomplete or stale information encountered in the relevant context, but only from repository evidence. Do not infer unsupported behavior. 5. Add a new context file when a new module, page, or independently maintained feature surface has no owner. Add its source mapping to `index.md`. 6. Preserve the standard section order: ```text # <Area> Context Sources Last verified Purpose Responsibilities / Current behavior Contracts and invariants Interactions Verification Major Changes ``` Omit a section only when it truly does not apply. Keep paths repository-relative and wrap them in backticks. ## Major change rule Record a major change when it alters at least one of these: - a public CLI command, HTTP/SSE API, persisted schema, config contract, role protocol, or module boundary; - a page-level