agentleFS
vishalguptaxvishalguptax/claude-code-manager/.claude/skills/release/SKILL.md

release

Skill32 starsChanged 48 days agoApache-2.0View on GitHub

Curate a release for the Claude Manager extension — analyze git commits since last tag, categorize them, generate a release notes markdown file in docs/releases/, decide the correct version bump, update CHANGELOG.md, and push a commit that triggers the CI/CD workflow to publish.

  • 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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 3

    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. Distinctive:

    Use this skill when the user says "release", "cut a release", "ship it", or similar.

    line 8
  2. Distinctive:

    If not on main, ask the user whether to merge the current branch first

    line 24
  3. Very specific:

    Check there's anything to release: git log $(git describe --tags --abbrev=0)..HEAD --oneline must be non-empty

    line 25
  4. Distinctive:

    If no commits since last tag, stop and tell the user there's nothing to release.

    line 27
  5. Very specific:

    Read the list. Ignore commits authored by github-actions[bot] (those are auto-bumps).

    line 40
  6. Very specific:

    Read current version from package.json:

    line 70
  7. Very specific:

    Create a new file at docs/releases/v{nextVersion}.md with this structure:

    line 80
  8. Very specific:

    Create a GitHub Release with the .vsix attached, using the content of docs/releases/v{nextVersion}.md as the release body (workflow reads …

    line 174
  9. Very specific:

    If the user hasn't added the VSCE_PAT / OVSX_TOKEN secrets, the publish steps are skipped silently but the GitHub Release still gets …

    line 197

“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

Use this skill when the user says "release", "cut a release", "ship it", or similar.

This skill curates a release for the Claude Manager VS Code extension. The CI/CD workflow (.github/workflows/release.yml) handles the actual version bump, build, packaging, and publish to the Marketplaces — this skill just prepares human-readable release notes and decides the bump level via the commit message.


Flow

1. Verify git state

git status
git branch --show-current
  • Working tree must be clean (no uncommitted changes)
  • If not on main, ask the user whether to merge the current branch first
  • Check there's anything to release: git log $(git describe --tags --abbrev=0)..HEAD --oneline must be non-empty

If no commits since last tag, stop and tell the user there's nothing to release.

2. Gather commits since last release

LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
  git log --oneline
else
  git log $LAST_TAG..HEAD --oneline
fi

Read the list. Ignore commits authored by github-actions[bot] (those are auto-bumps).

3. Categorize commits

Group commits by conventional-commit prefix:

PrefixSection title
feat: / feature:Features
fix:Bug Fixes
perf:Performance
refactor:Refactoring
docs:Documentation
style:UI/Styling
test:Tests
build: / chore: / ci:Build / CI
anything elseOther

Skip commits that are purely version bumps (release: v1.2.3) or merge commits (Merge branch) unless they carry meaningful content.

4. Decide bump level

Inspect commit messages to determine patch / minor / major:

  • Major: any commit message contains [major] or starts with breaking: or BREAKING CHANGE
  • Minor: any commit message contains [minor] or starts with feat: or feature:
  • Patch: anything else (fixes, chores, docs, perf, refactor, style)

5. Compute next version

Read current version from package.json:

node -p "require('./package.json').version"

Apply the bump rule to get the next version (e.g., 1.1.1 + minor → 1.2.0).

6. Generate the release notes markdown

Create a new file at docs/releases/v{nextVersion}.md with this structure:

# v{nextVersion}

_Released YYYY-MM-DD_

<one-sentence summary of the release — what's the headline feature or theme>

## ✨ Features
- <feat: commit subject> ([short-sha](link-to-commit))
- ...

## 🐛 Bug Fixes
- <fix: commit subject> ([sha])
- ...

## ⚡ Performance
- ...

## 💅 UI / Styling
- ...

## 📦 Build / CI
- ...

## 📚 Documentation
- ...

## 🔧 Refactoring
- ...

## Other
- ...

---

**Full changelog**: https://github.com/vishalguptax/claude-code-manager/compare/{lastTag}...{nextVersion}

Skip empty sections. If a section has no commits, omit it entirely. Keep commit subjects as-is (don't paraphrase) but strip the feat: / fix: etc. prefix so the section headings carry the type info.

Links: use https://github.com/vishalguptax/claude-code-manager/commit/{full-sha} as the href, show the 7-char short SHA as the link text.

7. Update CHANGELOG.md at repo root

Prepend a new entry to CHANGELOG.md (create it if it doesn't exist) in this format:

# Changelog

## [{nextVersion}] - YYYY-MM-DD

<same one-sentence summary as the release notes file>

See [docs/releases/v{nextVersion}.md](docs/releases/v{nextVersion}.md) for full details.

## [{previousVersion}] - ...
...

This keeps the root CHANGELOG short and marketplace-friendly while the per-release files hold the full detail.

8. Commit everything

Stage the new release notes file and the updated CHANGELOG.md. Commit with a message that includes the bump keyword so the CI workflow picks the right level:

  • Patch: release: v{nextVersion} (no keyword needed, default is patch)
  • Minor: release: v{nextVersion} [minor]
  • Major: release: v{nextVersion} [major]

Example:

git add docs/releases/v1.2.0.md CHANGELOG.md
git commit -m "release: v1.2.0 [minor]"

9. Push

git push

The CI workflow .github/workflows/release.yml will:

  1. Run tests
  2. Build the extension
  3. Bump package.json version (same bump we computed, via the commit message keyword)
  4. Re-commit the version bump back to main as github-actions[bot]
  5. Tag {nextVersion}
  6. Package the .vsix
  7. Publish to VS Code Marketplace (if VSCE_PAT secret set)
  8. Publish to Open VSX (if OVSX_TOKEN secret set)
  9. Create a GitHub Release with the .vsix attached, using the content of docs/releases/v{nextVersion}.md as the release body (workflow reads the file)

10. Report back

Tell the user:

  • The new version number
  • The bump level (patch / minor / major)
  • How many commits are included
  • Where the release notes file was created
  • That CI is now handling the publish
  • Link to Actions: https://github.com/vishalguptax/claude-code-manager/actions

Guardrails

  • Never bump version in package.json directly — let the CI workflow do it to avoid conflicts.
  • Never create the git tag directly — CI creates it after bumping.
  • Never run npm publish or vsce publish locally — CI owns publishing.
  • Don't include bot commits in release notes (they're version bumps, not meaningful changes).
  • Don't release from a dirty tree — stop and ask the user to commit or stash first.
  • Don't release from a feature branch without asking — the main branch is the release source.
  • If the user hasn't added the VSCE_PAT / OVSX_TOKEN secrets, the publish steps are skipped silently but the GitHub Release still gets created — mention this in the report.

File expected by CI

The CI workflow expects the release notes file at:

docs/releases/v{version}.md

It uses body_path on the softprops/action-gh-release step to load the file content into the GitHub Release body. If the file is missing, the workflow falls back to GitHub's auto-generated release notes.

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.