Release

Skill brimtown/claude-fortress/.claude/skills/release

Bump version, commit, and tag a releaseFrom its SKILL.md

Install

npx -y skills add brimtown/claude-fortress --skill release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.6 KB, as published. Nobody here has run it

Release Workflow

Trigger on: "release", "bump version", "prepare release", "new version"

Instructions

When triggered, execute all steps (don't just show commands):

Determine version bump type from user input or ask:
- patch (0.3.0 → 0.3.1) - bug fixes
- minor (0.3.0 → 0.4.0) - new features
- major (0.3.0 → 1.0.0) - breaking changes
Run the release script:
```
bun run scripts/release.ts <type>
```
Stage all changes:
```
git add -A
```

Commit with version in message:

git commit -m "chore: release v<NEW_VERSION>"

Create annotated git tag with release notes:
```
git tag -a v<NEW_VERSION> -m "<RELEASE_NOTES>"
```
Write release notes summarizing what's in this release:
- Start with version header: v<VERSION> - <SHORT_TITLE>
- Group changes under ## New Features, ## Bug Fixes, ## Technical, etc.
- Be concise but descriptive
- Look at commits since last tag: git log $(git describe --tags --abbrev=0)..HEAD --oneline
Push commits and tags:
```
git push && git push --tags
```

Example

User: "release patch" → Run script with patch → git add -A → git commit -m "chore: release v0.3.1" → git tag -a v0.3.1 -m "v0.3.1 - Bug Fixes\n\n## Bug Fixes\n- Fixed crash on startup\n- Fixed save corruption" → git push && git push --tags

Viewing Release Notes

# View tag message
git tag -l -n99 v<VERSION>

# Create GitHub release from tag
gh release create v<VERSION> --notes-from-tag

SKILL.md

Release Workflow

Instructions

Example

Viewing Release Notes

Keep looking