Keep affected repository documentation and vault knowledge correct, short and in one place. Use in plots that require it during planned work, or when asked to maintain a named scope in freeform.
Installs into .claude/skills of the current project.
Are you the author of Groom?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ellebam-groom)
---
name: groom
description: "Keep affected repository documentation and vault knowledge correct, short and in one place. Use in plots that require it during planned work, or when asked to maintain a named scope in freeform."
---
# Groom
Maintain the documents the current change affects. This is scoped maintenance, not a repository overhaul or a vault-wide audit. The repository's and plot's documentation rules take precedence. This skill adds no mandatory duty to a plot that does not require it and grants no new edit, commit or external-write authority.
Read the changed behavior and its owning documents. Follow the plot's vault context and pointers to notes the change could make wrong. An opened note is not automatically a maintenance target. Keep one owner per fact and link to it from other documents.
Record every affected repository document and vault note with one action, update, cut, merge or move. Name the destination for merge or move. Put this list in `## Plan` for spine work, and in the existing session notes for freeform. Include the paths in the authorized scope. If no document is affected, write `none` and one sentence explaining why. Planning is read-only, and the current phase's authority still applies.
When edits are authorized, deliver the list before proof and review, or before the freeform handback. Replace wrong content in place, remove stale and repeated claims, merge useful detail into its owner and repair direct links, headings and entry routes. Preserve unique decisions and their reasons, safety gates and evidence a pending review needs. Follow the global writing standard. Do not add a second telling or polish unrelated content.
Use the existing vault ledger before opening or editing a note, retain first-touch ownership and update its digest after each write. Follow the existing named-path commit route at the handback. Never fold foreign changes into this work. Leave protected or out-of-scope repairs unchanged and report their paths and reasons.
Read the result as its user. Check facts against the changed behavior, follow affected links and confirm the owning route still reaches retained content. Run the applicable document, size and vault-area checks. A protected gap is a reported gap, not delivered maintenance.
Reviews check the same list and content. Finalize and close-out in plots that require this skill verify its delivery, never run it to make late edits. An unmet action stops for operator direction. The handback names the documents changed or explains why none changed.
