post-commit

post-commit is a skill for Claude Code from fusengine/agents. It costs 33 tokens per session (1,222 once invoked), scanned A, original, MIT.

A post-commit workflow that runs after a successful code commit. A changelog is a file that records what changed between software versions.

In plain words
What is it for?
Use it to update a changelog and plugin version after commits, based on whether the repository is a marketplace plugin.
Why use it?
It removes the repetitive work of checking the new commit, choosing the next patch version, and recording the change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions .claude-plugin.

Part of the fuse-commit-pro plugin — 4 skills, 10 commands, 1 agent shipped together

Good fit Use it to update a changelog and plugin version after commits, based on whether the repository is a marketplace plugin.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fusengine/agents/post-commit
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fusengine/agents --skill post-commit
Clone the repo
git clone --depth 1 https://github.com/fusengine/agents

Made for: Claude Code.

Or install fuse-commit-pro, the plugin that ships this one along with the rest of its 4 skills, 10 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for post-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/fusengine/agents/post-commit/github.svg)](https://agentmods.dev/skills/fusengine/agents/post-commit)
Your own site
<a href="https://agentmods.dev/skills/fusengine/agents/post-commit"><img src="https://agentmods.dev/badge/skills/fusengine/agents/post-commit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for post-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/fusengine/agents/post-commit"><img src="https://agentmods.dev/badge/skills/fusengine/agents/post-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01222
Opus 5.5 $0.00013 $0.00489
Sonnet 5.5 $0.00007 $0.00244
Haiku 4.5 $0.00003 $0.00122

Measured 1mo ago against content hash cb8e93f58782, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

post-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/commit-pro/skills/post-commit/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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). 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

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.

Read the full file on GitHub · 110 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 110 lines · 33 tokens per session scan A cb8e93f58782

Subscribe to this mod's changes

post-commit is a skill published in the GitHub repository fusengine/agents (34 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 1,222 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

radin-batch

Work backlog tasks via sub-agents, prioritized, one commit each; plans first the entries radin-record flagged as needing a plan. Use for "work through my backlog", or name an epic or task to run only those.

shortcuts/radin · 54 tokens

finalise-session

Run /handover then commit and push changes to git.

isvlasov/rageatc-oss · 15 tokens

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

branch-and-worktree-workflow

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…

cbrock84/headcount · 70 tokens

genshijin-commit

A guide for writing short Git commit messages in Conventional Commits format, a shared style that labels changes such as features, fixes, tests, and documentation. It supports Japanese and English and emphasizes explaining why a change was made.

InterfaceX-co-jp/genshijin · 88 tokens