document-commit-deploy

# Document, Commit & Deploy Clayrune's SHARED_RULES requires that every major change be documented, committed, and (if git-synced) pushed. This skill is the concrete playbook so it actually happens. ## Sequence Run these steps in order. Don't skip. If a step is genuinely N/A for the current change, say so out loud before moving on. ### 1. Identify what changed ```bash git status git diff --stat git diff ``` Read the diff carefully. Group changes by intent (feature / fix / refactor / docs). ### 2. Update documentation artifacts For each changed area, update the corresponding doc: - **CHANGELOG.md** — add a dated entry summarizing what changed and why. Follow the existing format in the file (date stamp, bullet list of changes, optional Rollback / Why sections). - **CLAUDE.md** — update if the change affects how future agents should work in this codebase (new conventions, architectural shifts, new must-do steps). - **README.md** — update if user-facing behavior, install, or quickstart changed. - **MEMORY.md** — update if the change introduces a load-bearing fact about the project that future sessions need to know (architecture, gotchas, decisions). Skip if the change is routine. - **AGENT_RULES.md / SHARED_RULES.md** — update only if a new must-do or must-not-do rule emerged. - **`docs/USER_GUIDE.md`** (Clayrune only) — update if **anything user-facing** changed: a new UI element, button, menu entry, sidebar item, settings toggle, keyboard shortcut, or any feature an en...