OpenParable
Skip to content
← Back to skills

Release CLI

Apps & Automation
release-cli

Release CLI is an Agent Skill for apps & automation published in the kubetail-org/kubetail repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create GitHub releases for the Kubetail CLI by tagging the repo with the appropriate semver version.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/kubetail-org/kubetail/blob/HEAD/.claude/skills/release-cli/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/release-cli, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Release Skill

Tag and push a new semver release for the cli component.

Steps

  1. Detect upstream remote — find the remote that points to kubetail-org/kubetail:

    git remote -v | grep 'kubetail-org/kubetail' | head -1 | awk '{print $1}'
    

    Store the result as {upstream}. If no remote matches, stop and ask the user which remote to use.

  2. Verify branch and state:

    • Run git fetch {upstream} to update remote refs
    • Run git status -uno to confirm working tree is clean
    • Run git rev-parse HEAD and git rev-parse {upstream}/main to confirm HEAD is at {upstream}/main

    If working tree is dirty or HEAD is not at {upstream}/main, stop and ask the user to resolve before continuing.

  3. Find latest CLI tag:

    git tag --list "cli/v*" | sort -V | tail -1
    
  4. Check for changes since latest tag — run:

    git log {latest-tag}..HEAD --oneline -- modules/cli/ modules/dashboard/ modules/shared/ dashboard-ui/
    
    • If no commits touch these paths, skip (no release needed)
  5. Determine new version using semver — analyze commits:

    • Patch (Z+1): bug fixes, tests, docs, refactors, chores, ci changes
    • Minor (Y+1, reset Z=0): new backwards-compatible features
    • Major (X+1, reset Y=0, Z=0): breaking changes

    Use conventional commit prefixes as hints (fix: → patch, feat: → minor, BREAKING CHANGE → major), but read the actual messages to make a judgment call.

  6. Confirm with user before tagging — present a summary:

    Component | Current tag  | New tag      | Reason
    ----------|--------------|--------------|-------
    cli       | cli/v0.3.1   | cli/v0.4.0   | new feature: dark mode support
    

    Wait for explicit user confirmation before proceeding.

  7. Tag and push:

    git tag -s cli/v{X.Y.Z} -m "release: cli/v{X.Y.Z}"
    git push {upstream} cli/v{X.Y.Z}
    

    Confirm the push succeeded.

Rules

  • NEVER skip the user confirmation step — always show the summary and wait for approval.
  • NEVER tag or push without user confirmation.
  • NEVER use --no-verify or --force when pushing tags.
  • If git status shows uncommitted changes, stop immediately and tell the user to commit or stash first.
  • If HEAD is not at {upstream}/main, stop immediately and tell the user to check out {upstream}/main first.