Agent skill

Version Bump

by dmkenney in dmkenney/xamal

Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md

MITAuto-check passedDevelopment

Install Version Bump

skills CLI
$ npx skills add dmkenney/xamal --skill version-bump -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dmkenney/xamal version-bump --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dmkenney/xamal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/version-bump .claude/skills/version-bump && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
version-bump
GitHub stars
106
Token cost
~911 tokens
SKILL.md length
433 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md

  • Works in 6 steps: Confirm the repo is clean and current.… → Bump @version in mix.exs. Change only… → Roll the changelog. In CHANGELOG.md → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Inputs, Steps and Do not
  • Calls git; needs HEX_API_KEY

What it does

Version Bump is an agent skill from dmkenney/xamal. Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Elixir. The repository describes itself as: Deploy Elixir apps to bare metal servers. Like Kamal, but with native releases + Caddy instead of Docker. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/version-bump”

Requirements

  • A credential in HEX_API_KEY

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the repo is clean and current. Run git fetch and check the
  2. Bump @version in mix.exs. Change only the @version "..." attribute
  3. Roll the changelog. In CHANGELOG.md
  4. Verify the wiring is still correct (these are derived, not edited — confirm
  5. Run mix ci. It must pass clean (credo, architecture policy, dialyzer 0
  6. Report the two files changed (mix.exs, CHANGELOG.md), the version

What it can do on your machine

Read from SKILL.md and the folder at commit 830bd63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • HEX_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Version Bump loads about 911 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~911

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dmkenney/xamal at commit 830bd63, republished under its MIT licence (© dmkenney). 433 words, ~911 tokens.

Download SKILL.mdSave it as .claude/skills/version-bump/SKILL.md (or your agent's skills folder).
name
version-bump
description
Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md
metadata.version
1.0.0

Version bump

Prepare the repository for a new release locally. This skill never commits, tags, pushes, or publishes — it only edits files and verifies them. Use the release skill for the privileged steps (those need push rights / HEX_API_KEY).

Inputs

  • The target version (e.g. 0.3.3). If the user didn't give one, infer from the unreleased changes and SemVer, then confirm:
    • Bug fixes only → patch (0.3.2 → 0.3.3)
    • New backwards-compatible features → minor (0.3.2 → 0.4.0)
    • Breaking changes → major (0.3.2 → 1.0.0), or minor while 0.x
  • Read the current version from mix.exs (@version "...").

Steps

  1. Confirm the repo is clean and current. Run git fetch and check the working tree is clean and the local branch is not behind its remote. If the remote has moved, stop and tell the user to integrate first — tagging a stale commit is the failure mode this skill exists to prevent.

  2. Bump @version in mix.exs. Change only the @version "..." attribute (line ~4). Everything else (package(), docs(), source_ref) is derived from it — do not touch those.

  3. Roll the changelog. In CHANGELOG.md:

    • Rename the ## [Unreleased] heading to ## [x.y.z].
    • Add a fresh empty ## [Unreleased] section above it (so contributors always have a target for the next cycle).
    • Add a tag-link line at the bottom in the existing style: [x.y.z]: https://github.com/dmkenney/xamal/releases/tag/vx.y.z
    • Keep the existing Keep-a-Changelog format (### Added/Changed/Fixed/Removed, no dates). Do not switch formats.
    • If ## [Unreleased] is empty, draft entries from git log <prev-tag>..HEAD --oneline and the PR titles, then ask the user to review them. Never invent user-facing notes for internal/CI-only commits without flagging them.
  4. Verify the wiring is still correct (these are derived, not edited — confirm they didn't drift):

    • README.md install snippet uses a ~> constraint (e.g. {:xamal, "~> 0.3", ...}). It should only change on a major/minor boundary that moves the constraint, never on a patch. Leave it alone unless the new version crosses that boundary.
    • mix.exs docs() source_ref: "v#{@version}" and package() links still point at the right places (they're derived — just sanity-check).
  5. Run mix ci. It must pass clean (credo, architecture policy, dialyzer 0 errors, all tests). If it fails, stop and report — do not proceed.

  6. Report the two files changed (mix.exs, CHANGELOG.md), the version delta, and the changelog section that will become the release notes. Then hand off: tell the user the prep is done and the release skill (or a maintainer) handles commit → push → tag → publish.

Show full SKILL.md (44 more words)Show less

Do not

  • Do not git commit, git tag, git push, or mix hex.publish.
  • Do not edit package()/docs() directly or add a maintainers: field (Hex uses package owners via mix hex.owner, not the deprecated field).
  • Do not bump the README ~> constraint on a patch release.

© dmkenney, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/version-bump of dmkenney/xamal.

Open the folder on GitHubat commit 830bd63

Compare with similar skills

Version Bump next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Version Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Bump this skilldmkenney/xamal106—~911Automated safety check: PassMIT
Deps Updateoliver-kriska/claude-elixir-phoenix565—~1.4kAutomated safety check: PassMIT
Phx Deps Updateoliver-kriska/claude-elixir-phoenix565—~1.3kAutomated safety check: PassMIT
Phx Deps Updateoliver-kriska/claude-elixir-phoenix565—~1.3kAutomated safety check: PassMIT
Hexdocs Fetcheroliver-kriska/claude-elixir-phoenix565—~826Automated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT

Similar skills

  • Deps Update

    oliver-kriska/claude-elixir-phoenix

    Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo).

    565 GitHub stars~1.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Phx Deps Update

    oliver-kriska/claude-elixir-phoenix

    Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo).

    565 GitHub stars~1.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Phx Deps Update

    oliver-kriska/claude-elixir-phoenix

    Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo).

    565 GitHub stars~1.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Hexdocs Fetcher

    oliver-kriska/claude-elixir-phoenix

    Fetch HexDocs for Elixir libraries with HTML-to-markdown conversion.

    565 GitHub stars~826 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

More from dmkenney/xamal

  • Release

    dmkenney/xamal

    Cut a Xamal release end-to-end (maintainer-only). An agent skill from dmkenney/xamal.

    106 GitHub stars~873 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Version Bump

What does Version Bump do?

Prepare a new Xamal version locally — bump @version in mix.exs, roll the CHANGELOG.md. Version Bump is an agent skill from dmkenney/xamal.

When should I use Version Bump?

Version Bump fits situations like: tasks that involve Changelog and release notes.

How do I install Version Bump in Claude Code?

Run `npx skills add dmkenney/xamal --skill version-bump -a claude-code`. Or copy the skill folder (.claude/skills/version-bump in dmkenney/xamal) into .claude/skills/version-bump in your project. Claude Code loads it when a task matches its description.

How do I install Version Bump in Codex?

Run `npx skills add dmkenney/xamal --skill version-bump -a codex`. Or copy the skill folder (.claude/skills/version-bump in dmkenney/xamal) into .agents/skills/version-bump in your project. Codex loads it when a task matches its description.

Can I use Version Bump in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dmkenney/xamal --skill version-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-bump, .gemini/skills/version-bump, .github/skills/version-bump and .opencode/skills/version-bump in your project.

What does Version Bump need to run?

Going by SKILL.md and its folder, Version Bump needs the command-line tools its instructions call (git) and credentials named HEX_API_KEY. Our summary lists: A credential in HEX_API_KEY.

Does Version Bump access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Version Bump safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Version Bump use?

Version Bump is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Bump use?

About 911 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Version Bump?

Skills that share tags, products or a category with Version Bump: Deps Update (oliver-kriska/claude-elixir-phoenix, 565 stars), Phx Deps Update (oliver-kriska/claude-elixir-phoenix, 565 stars), Phx Deps Update (oliver-kriska/claude-elixir-phoenix, 565 stars) and Hexdocs Fetcher (oliver-kriska/claude-elixir-phoenix, 565 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Bump?

dmkenney (a GitHub user) maintains it in dmkenney/xamal, which has 106 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: dmkenney/xamal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.