A workflow for increasing a software project's version number and recording the changes in its changelog. Version numbers identify successive releases of a project.

Use it on a feature branch to choose and confirm a new version, update package.json and CHANGELOG.md, summarize branch changes, and create the specified commit.

It keeps the package version, release notes, and commit history aligned before a pull request is opened.

How nirelbaz/promptpit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nirelbaz/promptpit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nirelbaz/promptpit/main/.claude/commands/version.md

Clone the repo

git clone --depth 1 https://github.com/nirelbaz/promptpit

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nirelbaz/promptpit/version/github.svg)](https://agentmods.dev/commands/nirelbaz/promptpit/version)

Your own site

<a href="https://agentmods.dev/commands/nirelbaz/promptpit/version"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/version/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nirelbaz/promptpit/version"><img src="https://agentmods.dev/badge/commands/nirelbaz/promptpit/version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 239 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00239
Opus 5.5	$0.00000	$0.00096
Sonnet 5.5	$0.00000	$0.00048
Haiku 4.5	$0.00000	$0.00024

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

Security

Grade A, and why

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

.claude/commands/version.md · 16 lines

What it actually says

Bump the version and add a CHANGELOG entry. Run this on your feature branch before opening a PR that you want to release.

Steps

Determine the new version. If the user provided a version argument like $ARGUMENTS, use that. Otherwise, read the current version from package.json and bump the patch number (e.g., 0.1.4 → 0.1.5). Ask the user to confirm the version before proceeding.
Update package.json. Set the version field to the new version.
Update CHANGELOG.md. Add a new entry at the top (below the # Changelog heading) with the format:
```
## X.Y.Z (YYYY-MM-DD)
```
Summarize what changed on this branch by reading git log origin/main..HEAD. Write user-facing bullet points (what they can now do), not implementation details. Match the tone of existing entries.
Commit. Stage only package.json and CHANGELOG.md, commit with message: chore: bump version to X.Y.Z

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.

1mo ago First seen · 16 lines · 0 tokens per session scan A 6909c7155a5b

Subscribe to this mod's changes

version is a command published in the GitHub repository nirelbaz/promptpit (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 239 tokens. 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-08-31.

Claude Code Git and workflow Releases agent ai cli cursor developer-tools

promptpit: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

What this file has done since we first saw it

Other commands, from other repositories

bump-plugin

OPSX: Archive

openspec-archive

CHANGELOG

get-unpublished-changes

post-release.en