mc-changelog-updatelisted

# CHANGELOG.md update — guided Most Clayrune-managed projects keep a CHANGELOG.md in the project root. This skill walks through adding an entry that matches the project's existing format. ## Steps ### 1. Read the current CHANGELOG.md ```bash head -120 CHANGELOG.md ``` Pattern-match the existing style: - **Date stamp format** — `[2026-05-10]`, `## 2026-05-10`, `[v1.4.2 — 2026-05-10]`, etc. - **Section style** — flat bullets, or grouped under `### New`, `### Changed`, `### Fixed`? - **Voice** — past tense ("Added X") or imperative ("Add X")? - **Detail level** — one-line bullets, or paragraphs with Why/Rollback subsections? ### 2. Compose the entry Match the style exactly. Don't introduce a new format. Common structures: **Style A — flat bullets:** ```markdown ## [2026-05-10] — Short headline - Added foo - Fixed bar in baz - Removed deprecated quux ``` **Style B — grouped:** ```markdown ## [2026-05-10] — Short headline ### Added - New foo widget for X ### Fixed - bar no longer crashes when Y ### Changed - baz default flipped to true ``` **Style C — narrative with Why/Rollback:** ```markdown ## [2026-05-10] — Short headline - **Change:** One-sentence description of what changed. - **Why:** The motivation — incident, requirement, user request. - **Rollback:** How to revert if needed. ``` ### 3. Insert at the top (most projects) — or at the bottom (rarely) Most CHANGELOG.md files have newest entries at the top. Confirm by checking the existing first few entries: