agentleFS
kubetail-orgkubetail-org/kubetail/.claude/skills/release-version/SKILL.md

release-version

Skill1.8k starsChanged 7 days agoApache-2.0View on GitHub

Recommend the next release version of a Kubetail component (cli, dashboard, cluster-api or cluster-agent) under SemVer 2.0.0. Use when asked which version to release or tag next.

10 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the kubetail-org/kubetail repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about kubetail-org/kubetail

The biggest 5 of 27 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 27

Talked about on GitHub, Bluesky and Hacker News (27 times).

On GitHub · 20

15 more on GitHub

On Bluesky · 5

On Hacker News · 2

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read each commit's body as well (git log --format=%B -1 <sha>) for a BREAKING CHANGE: or BREAKING-CHANGE: footer.

    line 58
  2. Distinctive:

    If the list is empty, say there is nothing to release and stop.

    line 61
  3. Very specific:

    If that gives X.Y.Z or lower, X.Y.Z already holds these changes.

    line 115
  4. Very specific:

    If it gives a higher version, the changes outgrow X.Y.Z: recommend that higher version, and offer its first prerelease (-rc.1) beside it.

    line 118
  5. Very specific:

    The old form (rc1): Every prerelease tagged so far uses it (dashboard/v0.17.0-rc3).

    line 126
  6. Very specific:

    Never recommend build metadata (+…).

    line 131
  7. Very specific:

    Check too that the tag does not exist yet (git rev-parse -q --verify refs/tags/<tag> prints nothing) and that it sorts above the last …

    line 142

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Recommend the next release version

Recommend the next version of one component, given as the argument: cli, dashboard, cluster-api or cluster-agent. If the argument is missing or is anything else, ask which component and stop.

This skill recommends and nothing else. It never creates or pushes a tag, edits a file or dispatches a workflow. A person tags with the release-cli or release-cluster skill.

The rules are SemVer 2.0.0.

The components

ComponentTagWorkflowsPaths
clicli/v<version>release-cli.yml, release-docker.ymlmodules/cli/ modules/dashboard/ modules/shared/ dashboard-ui/
dashboarddashboard/v<version>release-docker.ymlmodules/dashboard/ modules/shared/ dashboard-ui/
cluster-apicluster-api/v<version>release-docker.ymlmodules/cluster-api/ modules/shared/ proto/
cluster-agentcluster-agent/v<version>release-docker.ymlcrates/ proto/

Each component's full list, with its Dockerfile and default config, is its release-<component> filter in .github/ci-config/path-filters.yml. Use those globs as the paths below. The CLI embeds the Dashboard, so the Dashboard's changes are the CLI's too.

1. Find the last release

Fetch tags first, so a tag pushed from elsewhere is seen: git fetch --tags --quiet against the remote that points to kubetail-org/kubetail. If the fetch fails, carry on with the local tags and say so.

List the component's tags (git tag -l '<component>/v*') and take the highest by SemVer precedence, not by date or by sort -V. Precedence (SemVer §11):

  1. Compare major, minor and patch as numbers.
  2. With those equal, a version with a prerelease sorts before the one without (1.0.0-rc.1 < 1.0.0).
  3. Two prereleases compare identifier by identifier, split on .. A numeric identifier compares as a number and sorts before an alphanumeric one; alphanumeric identifiers compare in ASCII order. With all shared identifiers equal, the shorter list sorts first.
  4. Build metadata (+…) is ignored.

Skip a tag whose version is not SemVer (step 5), and say you skipped it. If the component has no tag, say so and stop.

2. Collect the commits

git log --no-merges --format='%h%x09%s' <last-tag>..HEAD -- <paths>

Read each commit's body as well (git log --format=%B -1 <sha>) for a BREAKING CHANGE: or BREAKING-CHANGE: footer. A squash-merged PR's body may list several commits; read it whole.

If the list is empty, say there is nothing to release and stop.

3. Classify each commit

From the conventional-commit header, type(scope)!: subject:

HeaderLevel
! after the type or scope, or a breaking footermajor
featminor
fix, perfpatch
docs, test, chore, refactor, ci, style, buildnone

A header that is not a conventional commit gets no level from its header: read its diff. A build(deps) or fix(deps) bump counts as a patch when it changes what ships (a Go module, a crate or an npm package the component uses), and as none when it touches only tests or tooling.

Read the diff (git show --stat <sha>, then the relevant hunks) when the type looks wrong for the change. For example, a refactor that renames a CLI flag or a config key, a chore that changes what a user sees, or a fix that removes a behaviour someone relied on. A commit under modules/shared/ or proto/ counts only for the components whose code it changes. Classify by what the change does to the component's users, and name each commit you reclassified and why.

What counts as breaking:

  • cli: removing or renaming a command, flag, argument or config key, changing an exit code, or changing output a script may parse.
  • dashboard: removing or renaming a flag, environment variable or config key, or needing a permission the Helm chart's current release does not grant. Its GraphQL API serves its own UI alone; a change there is not breaking.
  • cluster-api: the same as the Dashboard, plus removing or changing a GraphQL field that a released Dashboard or kubetail logs reads, since a cluster runs them at different versions.
  • cluster-agent: the same as the Dashboard, plus a change to the gRPC contract in proto/ that a released Cluster API cannot speak.

The release's level is the highest level among the commits. If it is none, say there is nothing to release and stop.

4. Pick the version

Let the last release be X.Y.Z, with or without a prerelease.

From a release (X.Y.Z, no prerelease):

  • At 1.0.0 or later: major → (X+1).0.0, minor → X.(Y+1).0, patch → X.Y.(Z+1).
  • Before 1.0.0: a breaking change or a feat bumps the minor, 0.Y.Z → 0.(Y+1).0; a fix or perf bumps the patch, 0.Y.(Z+1). SemVer leaves 0.x unstable, and this is the convention every component keeps. Say plainly when this rule applies.
  • A bump resets every field below it (0.3.4 → 0.4.0).

From a prerelease (X.Y.Z-<pre>): first find the version the prerelease leads to. Apply the release's level, by the rules above, to the highest release tag of the component below X.Y.Z (0.0.0 when there is none).

  • If that gives X.Y.Z or lower, X.Y.Z already holds these changes. Offer both: the next prerelease of X.Y.Z, and X.Y.Z itself. Recommend one and say why (more changes to test favours the prerelease; a fix-only run after a tested candidate favours the release).
  • If it gives a higher version, the changes outgrow X.Y.Z: recommend that higher version, and offer its first prerelease (-rc.1) beside it.

The next prerelease increments the last numeric identifier: rc.1 → rc.2, beta.3 → beta.4; one with no numeric identifier gains .1 (beta → beta.1). Recommend dot-separated numbers (rc.1, rc.2) for a new version: rc10 sorts before rc2, since an alphanumeric identifier compares as text.

The old form (rc1). Every prerelease tagged so far uses it (dashboard/v0.17.0-rc3). Do not switch forms within one version: 0.17.0-rc.2 sorts before 0.17.0-rc1 (rc < rc1). The next prerelease of a version in the old form is rc<n+1>, and the dotted form starts with the next version. Say this when it applies.

Never recommend build metadata (+…).

5. Check the version

The version must match SemVer without build metadata, which tools/releasenotes and the workflows' prerelease check (a - in the version) rely on:

^(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-[0-9A-Za-z-]+(\.[0-9A-Za-z-]+)*)?$

Check too that the tag does not exist yet (git rev-parse -q --verify refs/tags/<tag> prints nothing) and that it sorts above the last release. If any check fails, fix the recommendation before printing it.

6. Report

Print, in this order:

  1. Recommended version, and the alternative when step 4 offers two.
  2. Last release: its tag and commit.
  3. Bump level: major, minor or patch, and the rule that turned it into this version (the 0.x rule, a prerelease, or none).
  4. Commits that drove it: each commit at the release's level as sha subject, then a count of the lower-level and no-level commits. Name any commit reclassified from its diff.
  5. Helm chart changes: for a cluster component, each commit whose PR says the chart needs a new permission, Secret, port, environment variable or config key. The chart, in kubetail-org/helm-charts, must ship it with this release.
  6. Next step: tag it with /release-cli or /release-cluster, then write the notes with /release-notes <component> <tag>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.