post-commit

# Post-Commit Skill Universal post-commit actions after a successful code commit. ## Step 1: Read Last Commit ```bash git log --format='%s' -1 ``` Save the commit message for CHANGELOG entry. ## Step 2: Detect Repo Type Check if `.claude-plugin/marketplace.json` exists in the repo root. - **EXISTS** → Follow **Marketplace Path** (Steps M1–M5) - **DOES NOT EXIST** → Follow **Standard Path** (Steps S1–S2) ## Standard Path (any repo without marketplace.json) ### Step S1: Update CHANGELOG Read the latest git tag to determine current version: ```bash git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0" ``` Increment PATCH: `X.Y.Z` → `X.Y.(Z+1)`. Add a new entry at the top of `CHANGELOG.md` (create it with a `# Changelog` heading first if missing). Load `references/changelog-templates.md` for the exact entry format and `references/changelog-type-mapping.md` for the commit-type prefix. ### Step S2: Commit CHANGELOG ```bash git add CHANGELOG.md git commit -m "$(cat <<'EOF' chore: update CHANGELOG to X.Y.Z EOF )" ``` STOP. Output summary. **No tag here** — it is created POST-MERGE by the `commit` command's Step 8 (or locally-only in LOCAL/DEGRADED mode when no remote/`gh` is available — see the Step 7 decision tree in `commands/commit.md`). Load `references/tag-timing.md` for the full post-merge rationale and the standalone-use exception. ## Marketplace Path (repo with .claude-plugin/marketplace.json) ### Step M1: Detect Modified Plugins ```bash git diff --nam...