RE

release-bump

Automates release versioning and changelog management.

Install

mkdir -p .claude/skills/release-bump-himatts && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12867" && unzip -o skill.zip -d .claude/skills/release-bump-himatts && rm skill.zip

Installs to .claude/skills/release-bump-himatts

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare versioned release updates for Lime Pipeline. Use when user-visible behavior changes require bumping `bl_info["version"]`, updating `CHANGELOG.md`, and producing release-ready QA notes.
192 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Choose bump level based on user-visible impact
  • Update `bl_info["version"]`
  • Add dated entry in `CHANGELOG.md`
  • Run QA baseline tests
  • Run `registration-audit` if ops/ui changed
  • Build artifact and record SHA256 hash

How it works

This skill prepares versioned release updates by choosing a bump level, updating version information, adding changelog entries, running QA tests, and building a release artifact with its hash.

Inputs & outputs

You give it
user-visible behavior changes
You get back
updated version tuple, changelog entry, QA summary, and artifact hash

When to use release-bump

  • Bump project version
  • Update changelog
  • Run QA suite
  • Build release artifact

About this skill

Goal

Create a consistent release increment with traceable version notes and build artifacts.

Steps

  1. Choose bump level (patch/minor/major) based on user-visible impact.
  2. Update bl_info["version"] in lime_pipeline/__init__.py.
  3. Add dated entry in CHANGELOG.md summarizing user-facing changes.
  4. Run QA baseline:
    • python -m unittest discover tests -v
    • poetry run mkdocs build
  5. If ops/ui changed, run registration-audit.
  6. Build artifact with package-addon and record SHA256 hash.

Outputs

  • Updated version tuple.
  • Changelog entry for the release.
  • QA command summary and artifact hash.

When not to use it

  • When user-visible behavior changes are not present
  • When not preparing versioned release updates for Lime Pipeline
  • When not needing QA notes

Limitations

  • Limited to Lime Pipeline releases
  • Requires `bl_info["version"]` in `lime_pipeline/__init__.py`
  • Requires `CHANGELOG.md` for entries

How it compares

This workflow provides a consistent and traceable release increment process for Lime Pipeline, including specific file updates and QA steps, which a manual release might not standardize.

Compared to similar skills

release-bump side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
release-bump (this skill)05moNo flagsIntermediate
code-change-verification44moReviewBeginner
discovering-make-commands35moNo flagsBeginner
django-verification54moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry