post-commit

Topics in the source

• Post-Commit Skill
• Step 0: Bump Range + Guard (run first, every time)
• Step 1: Read the Branch's Commits
• Step 2: Detect Repo Type
• Standard Path (any repo without marketplace.json)
• Step S1: Update CHANGELOG
• Step S2: Commit CHANGELOG
• Marketplace Path (repo with .claude-plugin/marketplace.json)

Runs universal post-commit actions after any non-wip/amend/undo code commit. Detects repo type: if .claude-plugin/marketplace.json exists, follows the Marketplace Path (bump each modified plugin's version, bump the suite version, recompute every README shields.io badge from the filesystem, check documentation parity for newly-added plugins); otherwise follows the Standard Path (CHANGELOG only). Updates CHANGELOG.md with a new entry and commits the bump as a commit separate from the code change. The git tag itself is NOT created here — it is created POST-MERGE by the commit command's Step 8 (or locally in LOCAL/DEGRADED mode when no remote/gh is available). Universal post-commit actions after a successful code commit. This block is the single source for the bump range: the commit command and agent point here, never restate it. --no-bump passed by the caller → skip this whole skill, unconditionally. Otherwise run: bump: skipped → STOP, report that line. A branch already bumped with nothing new since (a CI-fix or review round that only re-pushes) never stacks a second bump. bump: due → continue. If the branch was already bumped, only what changed after that bump is bumped again (plugi

This is an excerpt. Refer to the complete source and its current requirements.