Skip to content
Skills Library
Programming · Automation

fleet-release

/fleet-release

Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release everything on this branch". Handles dependency ordering (core first), automatic required_core_version sync, and tags each plugin immediately on main.

Repository
hermitd ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release everything on this branch". Handles dependency ordering (core first), automatic required_core_version sync, and tags each plugin immediately on main.

Triggers from the description

release both pluginsship them togetherrelease all changed pluginsfleet releasemulti-plugin releaserelease in orderrelease everything on this branch
Original author description

Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release everything on this branch". Handles dependency ordering (core first), automatic required_core_version sync, and tags each plugin immediately on main.

How it works

  1. Usage
  2. Steps
Original SKILL.md headings · 121 lines, 691 words
SKILL.md preview
---
name: fleet-release
description: Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release everything on this branch". Handles dependency ordering (core first), automatic required_core_version sync, and tags each plugin immediately on main.
---

# Fleet Release

Orchestrate a multi-plugin release: determines order, runs each plugin's `/release` prep sequentially, injects cross-plugin `hermit-meta.json` sync between core and domain plugins, tags each plugin on main.

**Runs on `main`.** Each plugin is committed, tagged, and pushed in order. No PR needed.

## Usage

```
/fleet-release [slug1 slug2 ...]   explicit list
/fleet-release                     auto-detect from current branch
/fleet-release --dry-run           show plan, no file changes
```

## Steps

### 1. Validate branch

Run `git branch --show-current`. If not on `main` or the repo's default branch: stop and tell the user to switch to main before running a fleet release.

### 1.5. Refresh the knowledge graph (fleet-wide)

`/release` only refreshes the root graph plus its own target plugin's graph (single-plugin scope). A fleet release touches multiple plugins at once, so refresh everything in one shot before the per-plugin `/release` runs:

```bash
bash scripts/graphify-refresh.sh
```

AST-only, no API cost. Skips silently if `graphify` isn't installed or the session is in a worktree; a single plugin's update failure warns and continues rather than aborting — a stale graph must never block a release.

### 2. Determine target plugins

**Explicit slugs:** validate each exists at `plugins/<slug>/.claude-plugin/plugin.json`. For any unknown slug, abort and list available slugs.

**Auto-detect (no args):** discover all slugs from `ls plugins/` (never hardcode or rely on session context), then collect plugins where both:
1. Files under `plugins/<slug>/` changed on this branch vs base: `git diff <base>..HEAD --name-only -- plugins/<slug>/` is non-empty
2. `plugin.json` version is ahead of the last `<slug>--v*` tag — same "already-bumped" detection as `/release` step 2

Skip plugins with no `plugin.json` version or no tags (unstructured). Note skipped plugins in output.

If condition 1 holds but condition 2 does not (branch changes but version not bumped yet): include the plugin and note it will need a full `/release` prep run.

### 3. Determine release order

Rule — not a graph:
1. `hermitd` goes first if present
2. Remaining plugins in the order the operator specified, or alphabetical for auto-detect

### 4. Determine version bumps and confirm upfront

For each plugin in order:
- If version is already ahead of last tag: mark as "already prepped at vX.Y.Z" — no bump step needed for it
- Otherwise: inspect `git log <last-tag>..HEAD -- plugins/<slug>/` to suggest patch/minor bump (same heuristics as `/release` step 2)

Present the full plan at once before touching any file:

```
Release plan:
  hermitd       1.0.22 → 1.0.23  (patch)
  hermitd-dev   already prepped at 0.2.2

Dep sync after core prep:
  hermitd-dev   required_core_version: >=1.0.22 → >=1.0.23

Confirm? [Yes / Adjust versions]
```

Wait for confirmation. If the user adjusts, accept corrections before continuing.

With `--dry-run`: stop here. Print the plan and exit without touching anything.

### 5. Run `/release` for core (if in fleet)

Invoke the full `/release hermitd` skill logic through the commit step, then:

```bash
git push origin main
```

Then run tag and push (`claude plugin tag --push`) and `gh release create`. The branch push must happen before tagging so the release commit is on the remote before the tag points to it.

### 6. Inject cross-plugin dep sync

Immediately after core's release commit and tag, before any domain plugin runs:

```bash
NEW_CORE=$(jq -r .version plugins/hermitd/.claude-plugin/plugin.json)
```

For each domain plugin **in the fleet** that has `plugins/<slug>/.claude-plugin/hermit-meta.json`:

```bash
jq --arg v ">=$NEW_CORE" '
  .required_core_version = $v |
  .requires["hermitd"] = $v
' plugins/<slug>/.claude-plugin/hermit-meta.json > tmp && mv tmp plugins/<slug>/.claude-plugin/hermit-meta.json
```

These changes will be staged and committed as part of each domain plugin's `/release` run in step 7 — no separate commit needed.

**Only update plugins in this fleet.** Plugins not being released are not touched.

### 7. Run `/release` for each domain plugin

For each domain plugin in order, invoke the full `/release <slug>` skill logic through the commit step, then:

```bash
git push origin main
```

Then tag and push (`claude plugin tag --push`) and `gh release create`. Always push the branch before tagging — same rule as step 5. The updated `hermit-meta.json` from step 6 will be included in the files that release commit touches.

### 8. Report

```
Fleet release complete:
  hermitd      v1.0.23  (commit abc1234, tag hermitd--v1.0.23)
  hermitd-dev  v0.2.3   (commit def5678, tag hermitd-dev--v0.2.3)
```
Files in this package (2)
  • SKILL.md 5 KB
  • trigger-evals.json 2 KB

Versions

RepositoryScoreLicence
This page · gtapps/hermitd100MIT
sturlabragason/fleet100MIT
gtapps/hermitd100MIT

Database snapshot: 13.11.2026 · package version 296c6423b27d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bump-core-req
    Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["hermitd"]` in `hermit-meta.json`, and the `dependencies` entry in `plugin.json`. Use this skill whenever the user says "bump core requirement",…
  • 100bump-core-req
    Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["hermitd"]` in `hermit-meta.json`, and the `dependencies` entry in `plugin.json`. Use this skill whenever the user says "bump core requirement",…
  • 84release
    Adds the release that every PR must carry, and runs before creating or pushing any PR. Bumps the plugin version and writes changelog entries: gathers merged PRs since the last tag plus unmerged current-branch changes, decides the semver bump, and commits the release onto the…
  • 90library-release
    Plan and prepare a shared-library release in any order (e.g. release Change B before Change A). Analyzes which changes a release needs, detects dependencies and conflicts, proposes a SemVer version, builds an isolated release branch, validates it, and prepares library and…
  • 100review-and-release
    Sync README with current agents/skills, validate plugin conventions, sync the Codex plugin directory (plugins/ai-kit), bump version, and commit. Use when the user says "/review-and-release" or wants to prepare a release after adding, removing, or changing agents or skills.
  • 100create-release
    Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.