timerise-ai

Bumpv — Documentation skill for Claude Code

Documentation community

Agent Skill: cut a Semantic Versioning release in any git repository.

How to install Bumpv

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerise-ai/bumpv and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Bumpv does

Agent Skill: cut a Semantic Versioning release in any git repository. Find the version source, decide MAJOR, MINOR or PATCH from the commits since the last tag, update the manifest, changelog and README release line, then commit and create a verified annotated tag, leaving the push to you

Alternatives in Documentation

  • Daily Changelog — Create a brief, human-readable daily changelog from these recent commits 327 ★
  • Cut Release Changelog — Cut the release CHANGELOG section — GenAI IDP Accelerator 295 ★
  • Create Release — Create a tagged GitHub release with structured release notes 238 ★

README

bumpv

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to cut a Semantic Versioning release in any git repository: find the version source, decide MAJOR, MINOR or PATCH from the commits since the last tag, update the manifest, the changelog and any current-release line, then commit and create an annotated tag. It works for a Next.js app and equally for Rust, Python, Go, PHP, Ruby, .NET and Dart projects, and for markdown-only packages such as the Timerise Skills themselves.

**The annotated tag is both the output of this release and the input of the next one.** The bump level, the changelog and the tagged tree all come from committed history, so every rule here keeps that tag correct: a clean tree so it points at what was decided, the repository's prefix so the next run finds it, and an annotated tag so it survives `git push --follow-tags`.

This skill was written by the engineer who runs this release procedure on the repositories they maintain. The earlier implementation was a single-file release procedure. What it carries holds as a check, not a hope: the tree is verified clean before anything is decided, only the release's own files are staged, the tag is verified annotated with `git cat-file -t`, the version agrees across manifest, changelog, README and tag, and the push stays with the user. [`references/provenance.md`](references/provenance.md) has the rec