agentleFS
suxrobGMsuxrobGM/jobpilot/.claude/skills/release/SKILL.md

release

Skill113 starsChanged 9 days agoMITView on GitHub

Bump the unified JobPilot version (host + plugin), update the changelog, commit, and tag a new release

  • Commits and pushes

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the current version from all four files above.

    line 35
  2. Distinctive:

    If they differ, report the mismatch and reconcile to the highest before bumping.

    line 36
  3. Distinctive:

    Use the user's explicit version, else compute from the bump type, else bump patch.

    line 37
  4. Distinctive:

    Verify the new version is strictly greater than the current highest.

    line 38
  5. Very specific:

    No existing tag vX.Y.Z (git tag -l).

    line 43
  6. Very specific:

    Agent version floor: if the commits since the previous tag include a breaking change (a !

    line 56
  7. Distinctive:

    Do not push - the user pushes when ready.

    line 74
  8. Distinctive:

    Do not let the four version fields drift - bump all to the same value.

    line 75
  9. Very specific:

    Do not use --no-verify / --no-gpg-sign if hooks fail - report instead.

    line 76
  10. Distinctive:

    Do not amend a previous commit to roll the version - always a new commit.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 183 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

Release Skill

Cut a new JobPilot release. Host and plugin share one version and ship from one tag (vX.Y.Z), which triggers .github/workflows/release.yml - it builds the terminal binaries for all RIDs, publishes the GitHub Release (the terminal archives, which bundle the plugin tree), and syncs the plugin tree into the claude-plugins and codex-plugins marketplaces.

Usage

The user provides a version (e.g. 2.1.0) or a bump type (major, minor, patch). With no argument, default to a patch bump.

Context

  • Version source of truth (must stay in lockstep):
    • apps/terminal/JobPilot.Terminal.csproj - the <Version> element
    • plugin/.claude-plugin/plugin.json - "version"
    • plugin/.codex-plugin/plugin.json - "version"
    • package.json - "version"
  • Tag format: vX.Y.Z (matches the v* trigger in release.yml).
  • Changelog: CHANGELOG.md at the repo root, Keep a Changelog format, newest release first. The workflow also sets generate_release_notes: true for the GitHub Release.

Steps

  1. Determine the new version:
    • Read the current version from all four files above.
    • If they differ, report the mismatch and reconcile to the highest before bumping.
    • Use the user's explicit version, else compute from the bump type, else bump patch.
    • Verify the new version is strictly greater than the current highest.
  2. Pre-flight checks (stop and report on any failure - do not paper over):
    • Working tree is clean (git status).
    • Current branch is main (or ask if on another branch).
    • No existing tag vX.Y.Z (git tag -l).
  3. Bump version: set the new version in all four files.
  4. Update CHANGELOG.md (create it with a # Changelog header if missing):
    • List commits since the previous tag: git log <prev-tag>..HEAD --oneline (all commits if no tag exists).
    • Prepend a ## vX.Y.Z - YYYY-MM-DD section, grouping the changes under ### Added / ### Changed / ### Fixed as applicable. Summarize user-facing changes in plain language; fold internal chores/refactors into one line or omit them.
    • Skip merge commits and the release commit itself.
  5. Agent version floor: if the commits since the previous tag include a breaking change (a ! subject or BREAKING CHANGE, or a removed/renamed route or payload the host or skills call), list them and ask the user whether to raise MIN_AGENT_VERSION in apps/api/src/common/middleware/agent-version.ts to the new version. If yes, bump it, move the boundary cases in agent-version.test.ts, and say in the changelog intro that older agents are refused. Skip the question if the user already said in the arguments.
  6. Commit: stage the four version files + CHANGELOG.md (plus the agent-version files if bumped), commit chore: release vX.Y.Z.
  7. Tag: git tag -a vX.Y.Z -m "JobPilot vX.Y.Z".
  8. Report: show the new version and tag, and remind the user to run git push && git push origin vX.Y.Z to trigger release.yml.

Do NOT

  • Do not push - the user pushes when ready.
  • Do not let the four version fields drift - bump all to the same value.
  • Do not use --no-verify / --no-gpg-sign if hooks fail - report instead.
  • Do not amend a previous commit to roll the version - always a new commit.

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.