Post Commit

Post-Commit Skill

Universal post-commit actions after a successful code commit.

Step 1: Read Last Commit

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:

git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0"

Increment PATCH: X.Y.Z → X.Y.(Z+1).

If CHANGELOG.md does not exist, create it with # Changelog heading.

Add a new entry at the top (after the # Changelog heading):

## [X.Y.Z] - DD-MM-YYYY

- commit message from Step 1

Step S2: Git Tag

git add CHANGELOG.md
git commit -m "$(cat /dev/null | wc -l | tr -d ' ')
SKILLS=$(ls -d plugins/*/skills/*/ 2>/dev/null | wc -l | tr -d ' ')

Update each badge token in README.md so it matches reality (replace the token, not the whole line):

• version-v- → version-v-
• plugins-- → plugins-$PLUGINS-
• agents-- → agents-$AGENTS-
• skills-- → skills-$SKILLS-

sed -i '' -E "s/version-v[0-9.]+-/version-v${NEW}-/; s/plugins-[0-9]+-/plugins-${PLUGINS}-/; s/agents-[0-9]+-/agents-${AGENTS}-/; s/skills-[0-9]+-/skills-${SKILLS}-/" README.md

Step M3.5: Documentation Parity

For any plugin added in this commit, create its docs page and link it. Doc filenames are abbreviated (e.g. dir nextjs-expert → docs/plugins/nextjs.md), so match the existing naming in docs/plugins/, not the raw dir.

git diff --name-only HEAD~1 HEAD | grep -oE '^plugins/[^/]+' | sort -u   # plugins touched this commit

For each NEW plugin lacking a page:

1. Create docs/plugins/.md mirroring a sibling page (title, How It Works, Configuration, Commands, Scripts tables).
2. Add a row to the matching README plugin table and append the plugin to the /plugin install … command list.

Step M4: Update CHANGELOG

Add a new entry at the top of CHANGELOG.md (after the # Changelog heading):

## [X.Y.Z] - DD-MM-YYYY

- type(plugin-name): description from the code commit message

Where X.Y.Z is the new suite version from Step M3.

Include (plugin-name X.Y.Z) in each line for bumped plugins.

Step M5: Commit, Tag, and Push

Stage all modified files:

git add CHANGELOG.md README.md .claude-plugin/marketplace.json plugins/*/.claude-plugin/plugin.json docs/

Commit with HEREDOC format:

git commit -m "$(cat <<'EOF'
chore: bump marketplace and CHANGELOG to X.Y.Z
EOF
)"

This MUST be a separate commit from the code changes. Never combine.

Then tag and push:

git tag vX.Y.Z
git push origin vX.Y.Z

Only tag the bump commit. Never tag code commits.

---

Version Bump Rules

• ALL commit types trigger PATCH bump only
• MINOR/MAJOR bumps are manual user decisions, never automatic
• The bump commit is always SEPARATE from code changes

CHANGELOG Type Mapping

| Commit Type | CHANGELOG Prefix | |-------------|-----------------| | feat | Added | | fix | Fixed | | refactor | Changed | | docs | Documentation | | perf | Performance | | test | Tests | | chore | Maintenance | | style | Style | | ci | CI/CD | | build | Build |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: fusengine
• Source: fusengine/agents
• License: MIT

Install and usage instructions live in the source repository linked above.