agentleFS
gustavo-meilusgustavo-meilus/aiboarding/.claude/skills/cutting-a-release/SKILL.md

cutting-a-release

Skill2 starsChanged 3 months agoMITView on GitHub

Cut an aiboarding version release (vX.Y.Z) - verify the single version target agrees, draft matching CHANGELOG + RELEASE-NOTES entries, commit to main, then create the GitHub release + tag and verify. Use when the user asks to cut/ship/publish a release, tag a version, do release work, or write release notes for aiboarding.

  • Commits and pushes

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    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:

    No CI: No GitHub Actions gate - verification is rg/Read assertions + python3 -c "import json.

    line 13
  2. Very specific:

    One version target: Only .claude-plugin/plugin.json (version) carries the version.

    line 14
  3. Very specific:

    JSON must be BOM-free: Never Set-Content -Encoding UTF8 for JSON.

    line 15
  4. Very specific:

    gh CLI in Bash tool: never --body @'...'@ (PowerShell here-string, fails).

    line 17
  5. Very specific:

    Bump version if needed: - if the feature work did not already bump plugin.json, do it now (Edit tool, BOM-free).

    line 24
  6. Very specific:

    Draft doc entries: - add ## X.Y.Z to CHANGELOG.md (with trailing --- separator) and a <release_entry> to RELEASE-NOTES.md, mirroring the …

    line 25

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

Cutting an aiboarding Release

Cut a version release after the feature work is merged into main. Full step detail + gotchas live in RUNBOOK.md - read it before acting.

Hard constraints (read first)

  • main is NOT branch-protected. Direct git push origin main works; no PR or --admin dance required. (Confirm with the user if they prefer a PR anyway.)
  • No CI. No GitHub Actions gate - verification is rg/Read assertions + python3 -c "import json; json.load(...)". Nothing waits on green checks.
  • One version target. Only .claude-plugin/plugin.json (version) carries the version. marketplace.json has NO per-plugin version field - do not add one. There is no package.json / .version-bump.json / .cursor-plugin / CLAUDE.md version.
  • JSON must be BOM-free. Never Set-Content -Encoding UTF8 for JSON. Use the Edit tool or python3 writes (encoding="utf-8").
  • Tag ↔ changelog convention (stated in CHANGELOG.md header): every tag vX.Y.Z MUST have a matching ## X.Y.Z CHANGELOG entry and a ## vX.Y.Z RELEASE-NOTES entry before gh release create.
  • gh CLI in Bash tool: never --body @'...'@ (PowerShell here-string, fails). Write the body to a temp .md, use --body-file, then rm it. Keep temp files out of commits.
  • Title form: vX.Y.Z - <Title Case Feature Name> (matches existing releases).

Workflow

  1. Preflight - git fetch origin; confirm origin/main has the feature merge; verify plugin.json version equals the intended vX.Y.Z; check tag/release naming convention.
  2. Sync local main - git checkout main && git pull --ff-only origin main.
  3. Bump version if needed - if the feature work did not already bump plugin.json, do it now (Edit tool, BOM-free).
  4. Draft doc entries - add ## X.Y.Z to CHANGELOG.md (with trailing --- separator) and a <release_entry> to RELEASE-NOTES.md, mirroring the previous entry's format exactly; extend the <overview> milestone sentence and the Roadmap. Source bullets from real changes; do not invent.
  5. Commit to main - git add the changed files, commit, git push origin main. (No PR needed - main is open.)
  6. Create release + tag - extract the new CHANGELOG section as the release body, append the install line, gh release create vX.Y.Z --target main --title "vX.Y.Z - <Title>" --notes-file <tmp>.
  7. Verify - tag commit == origin/main; release not draft/prerelease; it shows as Latest.

Gotchas checklist

  • Bumped plugin.json version only - did NOT add a version field to marketplace.json.
  • plugin.json version == intended vX.Y.Z before tagging.
  • CHANGELOG (## X.Y.Z + ---) and RELEASE-NOTES (<release_entry> + overview + roadmap) entries exist before gh release create.
  • Used --body-file for all gh bodies (never @'...'@).
  • JSON edits BOM-free.
  • Temp files cleaned up, kept out of commits.

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.