release-automation-builder — Claude Code skill: releases and setup
release-automation-builder is a Claude Code skill for automating releases and package publishing. It responds to requests about versioning, changelogs, or release workflows.
MIT 265 installs ★ 64 updated 2026-01-12
npx skills add patricio0312rev/skills --skill release-automation-builder -a claude-codeWhat release-automation-builder does
release-automation-builder helps configure release flows with Changesets or semantic-release. It covers version updates, generated changelogs, Git tags, release notes, and publishing packages to npm or images to Docker Hub.
The Changesets example uses @changesets/cli and changeset, version, and release scripts in package.json. For semantic-release, the skill provides a .releaserc.js setup and a GitHub Actions workflow using GITHUB_TOKEN and NPM_TOKEN. The examples specify Node 20 and run npm ci and npm run build. Docker Hub publishing uses DOCKER_USERNAME and DOCKER_PASSWORD.
What it helps with
- configure version releases with Changesets
- generate changelogs and release notes
- publish npm packages and Docker images from GitHub Actions
- create Git tags as part of a release workflow
Example prompts for the agent
- Set up automated package releases with Changesets.
- Create a GitHub Actions workflow for publishing through semantic-release.
- Add Docker image publishing with a tag read from
package.json.
How to install release-automation-builder
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill release-automation-builder -a claude-code2Manually: put the files in place
~/.claude/skills/release-automation-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-automation-builder/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill release-automation-builder -a codex2Manually: put the files in place
.agents/skills/release-automation-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill release-automation-builder -a cursor2Manually: put the files in place
.cursor/skills/release-automation-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install patricio0312rev/skills ci-cd/release-automation-builder/SKILL.md2Manually: put the files in place
.github/skills/release-automation-builder/SKILL.md1Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill release-automation-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/patricio0312rev/skills --path ci-cd/release-automation-builderManually: put the files in place
.devin/skills/release-automation-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add patricio0312rev/skills --skill release-automation-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-automation-builder
How do I install release-automation-builder in Claude Code?
Run npx skills add patricio0312rev/skills --skill release-automation-builder -a claude-code. The skill file is located at ~/.claude/skills/release-automation-builder/SKILL.md.
What does release-automation-builder do?
It helps configure releases with Changesets or semantic-release, including version updates, changelogs, Git tags, release notes, and package publishing.
What does release-automation-builder need to work?
The Changesets example uses @changesets/cli and Node 20. The workflows use GITHUB_TOKEN and NPM_TOKEN; Docker Hub publishing also requires DOCKER_USERNAME and DOCKER_PASSWORD.
Source text
SKILL.md · MIT
---
name: release-automation-builder
description: Automates releases and package publishing with changesets or semantic-release. Handles versioning, changelog generation, git tags, and release notes. Use for "release automation", "semantic versioning", "package publishing", or "changelog generation".
---
# Release Automation Builder
Automate releases with versioning, changelogs, and publishing.
## Using Changesets
### Setup
```bash
npm install -D @changesets/cli
npx changeset init
```
### Workflow
```yaml
# .github/workflows/release.yml
name: Release
on:
push:
branches:
- main
concurrency: ${{ github.workflow }}-${{ github.ref }}
jobs:
release:
name: Release
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-node@v4
with:
node-version: "20"
cache: "npm"
- run: npm ci
- name: Create Release Pull Request or Publish
uses: changesets/action@v1
with:
publish: npm run release
commit: "chore: release packages"
title: "chore: release packages"
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
```
### Package Scripts
```json
{
"scripts": {
"changeset": "changeset",
"version": "changeset version",
"release": "changeset publish"
}
}
```
## Using Semantic Release
### Configuration
```javascript
// .releaserc.js
module.exports = {
branches: ["main"],
plugins: [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/github",
[
"@semantic-release/git",
{
assets: ["CHANGELOG.md", "package.json"],
message:
"chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}",
},
],
],
};
```
### Workflow
```yaml
# .github/workflows/release.yml
name: Release
on:
push:
branches: [main]
jobs:
release:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
persist-credentials: false
- uses: actions/setup-node@v4
with:
node-version: "20"
- run: npm ci
- run: npm run build
- name: Release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
run: npx semantic-release
```
## Versioning Strategy
### Semantic Versioning (SemVer)
```
MAJOR.MINOR.PATCH
1.0.0 → 1.0.1 (patch - bug fix)
1.0.1 → 1.1.0 (minor - new feature)
1.1.0 → 2.0.0 (major - breaking change)
```
### Conventional Commits
```
feat: add new feature (minor bump)
fix: fix bug (patch bump)
perf: performance improvement (patch bump)
docs: update docs (no bump)
chore: maintenance (no bump)
feat!: breaking change (major bump)
fix!: breaking bug fix (major bump)
```
## Changelog Generation
```markdown
# Changelog
## [2.1.0] - 2024-01-15
### Added
- New dashboard widget (#123)
- Export to PDF feature (#125)
### Fixed
- Memory leak in data processing (#124)
- Typo in error message (#126)
### Changed
- Updated dependencies
## [2.0.0] - 2024-01-01
### Breaking Changes
- Removed deprecated API endpoints
- Changed authentication method
### Migration Guide
See MIGRATION.md for upgrade instructions
```
## Docker Image Publishing
```yaml
docker-release:
runs-on: ubuntu-latest
needs: test
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- name: Get version
id: version
run: echo "version=$(cat package.json | jq -r '.version')" >> $GITHUB_OUTPUT
- name: Login to Docker Hub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_PASSWORD }}
- name: Build and push
uses: docker/build-push-action@v5
with:
context: .
push: true
tags: |
mycompany/myapp:latest
mycompany/myapp:${{ steps.version.outputs.version }}
```
## NPM Publishing
```yaml
publish:
runs-on: ubuntu-latest
needs: test
if: github.event_name == 'release'
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "20"
registry-url: "https://registry.npmjs.org"
- run: npm ci
- run: npm run build
- name: Publish to npm
run: npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
```
## GitHub Release Notes
````yaml
- name: Create GitHub Release
uses: actions/create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag_name: v${{ steps.version.outputs.version }}
release_name: Release ${{ steps.version.outputs.version }}
body: |
## What's Changed
${{ steps.changelog.outputs.content }}
## Installation
```bash
npm install mypackage@${{ steps.version.outputs.version }}
```
draft: false
prerelease: false
````
## Best Practices
1. **Conventional commits**: Standardize commit format
2. **Protected branches**: Prevent direct pushes to main
3. **Automated versioning**: Let tools determine versions
4. **Changelogs**: Auto-generate from commits
5. **Git tags**: Tag every release
6. **Release notes**: Include migration guides
7. **Dry run**: Test releases in staging
## Output Checklist
- [ ] Changesets or semantic-release configured
- [ ] Versioning strategy documented
- [ ] Changelog generation automated
- [ ] Git tagging automated
- [ ] Release notes template
- [ ] NPM publishing (if package)
- [ ] Docker publishing (if applicable)
- [ ] Protected branch rules
© patricio0312rev · MIT · patricio0312rev/skills