Agent skill

Dev Bump

by Netis in Netis/heron

Bump Heron version via the VERSION-file SSOT. An agent skill from Netis/heron.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Dev Bump

skills CLI
$ npx skills add Netis/heron --skill dev-bump -a claude-code

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

GitHub CLI
$ gh skill install Netis/heron dev-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/Netis/heron.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dev-bump .claude/skills/dev-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
dev-bump
GitHub stars
102
Token cost
~983 tokens
SKILL.md length
388 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Bump Heron version via the VERSION-file SSOT. An agent skill from Netis/heron.

  • Works in 5 steps: Pre-flight → Bump → Update CHANGELOG.md → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Parameters, Workflow, Type: tag (no version change) and Guardrails, plus 1 more section
  • Calls just and git

What it does

Dev Bump is an agent skill from Netis/heron. Bump Heron version via the VERSION-file SSOT. Delegates to just bump which syncs server/Cargo.toml (workspace.package.version) and console/package.json. Also updates CHANGELOG.md and creates a bump commit + tag. Usage: /dev-bump <type where type=patch|minor|major|tag

Its SKILL.md is about 980 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 AI & LLM Engineering, covering Changelog and release notes, LLM inference and serving and LLM observability. It works with Rust, npm, Ollama and SGLang. The repository describes itself as: Agent and LLM API performance monitoring via network packet probe. Measures performance of OpenClaw, Claude, Codex, DeepAgents and more — deployed on the provider side, no SDK… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve LLM inference and serving
  • Tasks that involve LLM observability

Example prompts

  • “/dev-bump”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Pre-flight
  2. Bump
  3. Update CHANGELOG.md
  4. Commit and tag
  5. Sanity build (optional but recommended)

What it can do on your machine

Read from SKILL.md and the folder at commit 4f92b05. 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:

    • just
    • 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 no API keys, tokens, secrets or passwords.

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

Context cost

Dev Bump loads about 983 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 388 words of instructions outside code blocks.

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

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 Netis/heron at commit 4f92b05, republished under its Apache-2.0 licence (© Netis). 388 words, ~983 tokens.

Download SKILL.mdSave it as .claude/skills/dev-bump/SKILL.md (or your agent's skills folder).
name
dev-bump
description
Bump Heron version via the VERSION-file SSOT. Delegates to `just bump` which syncs server/Cargo.toml (workspace.package.version) and console/package.json. Also updates CHANGELOG.md and creates a bump commit + tag. Usage: /dev-bump <type> where type=patch|minor|major|tag
version
0.2.0

dev-bump — Version bump for Heron

Heron uses a VERSION-file SSOT pattern (see Core Principles → Single Source of Truth in AGENTS.md):

FileRole
VERSION (repo root)Canonical. Plain X.Y.Z + trailing newline. Every other version reference derives from here.
server/Cargo.toml (workspace.package.version)Derived — rewritten by just bump. Cargo requires a literal version string.
console/package.json (version)Derived — rewritten by just bump. npm tooling needs the literal.
server/h-common/src/version.rsReads VERSION via include_str! at compile time. Other Rust crates call h_common::version::version().
console/vite.config.tsReads VERSION at build time, exposes as __APP_VERSION__ for frontend code.

Parameters

  • type — patch | minor | major | tag | set X.Y.Z
    • patch: 0.1.0 → 0.1.1
    • minor: 0.1.0 → 0.2.0
    • major: 0.1.0 → 1.0.0
    • tag: no version change, just create v<current> git tag (for retagging or after a manual bump)
    • set X.Y.Z: set exact version (pre-release coordination, reverts)

Workflow

1. Pre-flight
bash
just bump check     # verifies VERSION == Cargo.toml == package.json
git status          # must be clean (or ask user to stash/commit first)

If just bump check shows drift, fix it before bumping: run just bump set <VERSION-value> to force Cargo.toml / package.json back in sync with VERSION (or vice versa — decide with the user which value is authoritative).

2. Bump
bash
just bump <type>    # patch | minor | major | set X.Y.Z

This rewrites VERSION, server/Cargo.toml, console/package.json atomically. Verify:

bash
just bump check
3. Update CHANGELOG.md

Create or update CHANGELOG.md at repo root using Keep-a-Changelog format:

markdown
## [0.2.0] — 2026-04-15

### Added
- ...

### Changed
- ...

### Fixed
- ...

Source entries from git log v<previous>..HEAD --oneline. Group by conventional-commit type (feat → Added, fix → Fixed, refactor/chore → Changed). Skip trivial commits (pure docs/test unless significant).

4. Commit and tag
bash
git add VERSION server/Cargo.toml console/package.json CHANGELOG.md
git commit -m "bump: v<new-version>"
git tag v<new-version>

Do not push automatically. Report the new tag back to the user; they decide when to push.

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

If the bump touches Rust or TS:

bash
just quality all

Catches the case where include_str! path drift or __APP_VERSION__ typing breaks after a refactor.

Type: tag (no version change)

For retagging the current VERSION value without changing it (e.g. after a manual VERSION edit, or re-tagging from a different commit):

bash
current="$(cat VERSION | tr -d '[:space:]')"
git tag "v$current"

Still update CHANGELOG if release notes changed.

Guardrails

  • Never edit Cargo.toml / package.json version fields directly. If you're tempted, it means just bump is broken — fix the script, not the derived files.
  • Never commit a drifted state. just bump check should be green before every bump commit.
  • Never push tags automatically. User decides.
  • Never rename VERSION. It is referenced by path from vite.config.ts, h-common/src/version.rs, scripts/routers/shared/bump.sh, and justfile.

Output format after a run

Report:

  1. Old → new version
  2. just bump check result (should be green)
  3. Commit hash and tag name created
  4. Reminder: user must git push && git push --tags when ready

© Netis, Apache-2.0. 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 .agents/skills/dev-bump of Netis/heron.

Open the folder on GitHubat commit 4f92b05

Compare with similar skills

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

Dev Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Bump this skillNetis/heron102—~983Automated safety check: PassApache-2.0
Debug InferenceNVIDIA/OpenShell15k—~1.9kAutomated safety check: PassApache-2.0
Agentsop LLM Engine Selectionagentsope/SkillAlchemy457—~6.1kAutomated safety check: PassMIT
LLM Torch Profiler Trace AnalysisBBuf/AI-Infra-Auto-Driven-SKILLS900—~2.8kAutomated safety check: PassNone
LLM Pipeline Profiler AnalysisBBuf/AI-Infra-Auto-Driven-SKILLS900—~3.9kAutomated safety check: PassNone
LLM Torch Profiler Analysissgl-project/sglang37k2 repos~6.4kAutomated safety check: PassApache-2.0

Similar skills

  • Debug Inference

    NVIDIA/OpenShell

    Official

    Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM.

    15k GitHub stars~1.9k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Agentsop LLM Engine Selection

    agentsope/SkillAlchemy

    Cross-engine decision rubric for self-hosting or recommending an LLM serving stack.

    457 GitHub stars~6.1k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check passed
  • LLM Torch Profiler Trace Analysis

    BBuf/AI-Infra-Auto-Driven-SKILLS

    Analyzes Torch Profiler traces from SGLang, vLLM and TensorRT-LLM servers into kernel attribution, overlap and fusion tables.

    900 GitHub stars~2.8k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • LLM Pipeline Profiler Analysis

    BBuf/AI-Infra-Auto-Driven-SKILLS

    Breaks LLM torch profiler traces down by forward pass, layer and kernel, with timing tables and Perfetto time ranges for the layers you want to inspect.

    900 GitHub stars~3.9k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • LLM Torch Profiler Analysis

    sgl-project/sglang

    Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.

    37k GitHub starsUsed in 2 repos~6.4k tokens
    DevelopmentAuto-check passed
  • Official

    Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.

    11k GitHub starsUsed in 1 repo~4.6k tokens
    AI & LLM EngineeringAuto-check passed

More from Netis/heron

  • Sync documentation with project state using ICAV workflow. An agent skill from Netis/heron.

    102 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed

Questions about Dev Bump

What does Dev Bump do?

Bump Heron version via the VERSION-file SSOT. An agent skill from Netis/heron. Dev Bump is an agent skill from Netis/heron. Bump Heron version via the VERSION-file SSOT.

When should I use Dev Bump?

Dev Bump fits situations like: tasks that involve Changelog and release notes; tasks that involve LLM inference and serving; tasks that involve LLM observability.

How do I install Dev Bump in Claude Code?

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

How do I install Dev Bump in Codex?

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

Can I use Dev 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 Netis/heron --skill dev-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/dev-bump, .gemini/skills/dev-bump, .github/skills/dev-bump and .opencode/skills/dev-bump in your project.

What does Dev Bump need to run?

Going by SKILL.md and its folder, Dev Bump needs the command-line tools its instructions call (just and git).

Does Dev 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 Dev 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 Dev Bump use?

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

How many tokens does Dev Bump use?

About 983 tokens (SKILL.md is roughly 3.9k 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 Dev Bump?

Skills that share tags, products or a category with Dev Bump: Debug Inference (NVIDIA/OpenShell, 15k stars), Agentsop LLM Engine Selection (agentsope/SkillAlchemy, 457 stars), LLM Torch Profiler Trace Analysis (BBuf/AI-Infra-Auto-Driven-SKILLS, 900 stars) and LLM Pipeline Profiler Analysis (BBuf/AI-Infra-Auto-Driven-SKILLS, 900 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Bump?

Netis (a GitHub organization) maintains it in Netis/heron, which has 102 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 4, 2026.

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