Back to skills
SkillHub ClubShip Full StackFull Stack
release
Automated release workflow for oh-my-claudecode
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
10,388
Hot score
99
Updated
March 20, 2026
Overall rating
C4.8
Composite score
4.8
Best-practice grade
C60.0
Install command
npx @skill-hub/cli install yeachan-heo-oh-my-claudecode-release
Repository
Yeachan-Heo/oh-my-claudecode
Skill path: skills/release
Automated release workflow for oh-my-claudecode
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: Yeachan-Heo.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install release into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/Yeachan-Heo/oh-my-claudecode before adding release to shared team environments
- Use release for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: release
description: Automated release workflow for oh-my-claudecode
---
# Release Skill
Automate the release process for oh-my-claudecode.
## Usage
```
/oh-my-claudecode:release <version>
```
Example: `/oh-my-claudecode:release 2.4.0` or `/oh-my-claudecode:release patch` or `/oh-my-claudecode:release minor`
## Release Checklist
Execute these steps in order:
### 1. Version Bump
Update version in all locations:
- `package.json`
- `src/installer/index.ts` (VERSION constant)
- `src/__tests__/installer.test.ts` (expected version)
- `.claude-plugin/plugin.json`
- `README.md` (version badge and title)
### 2. Run Tests
```bash
npm run test:run
```
All 231+ tests must pass before proceeding.
### 3. Commit Version Bump
```bash
git add -A
git commit -m "chore: Bump version to <version>"
```
### 4. Create & Push Tag
```bash
git tag v<version>
git push origin main
git push origin v<version>
```
### 5. Publish to npm
```bash
npm publish --access public
```
### 6. Create GitHub Release
```bash
gh release create v<version> --title "v<version> - <title>" --notes "<release notes>"
```
### 7. Verify
- [ ] npm: https://www.npmjs.com/package/oh-my-claude-sisyphus
- [ ] GitHub: https://github.com/Yeachan-Heo/oh-my-claudecode/releases
## Version Files Reference
| File | Field/Line |
|------|------------|
| `package.json` | `"version": "X.Y.Z"` |
| `src/installer/index.ts` | `export const VERSION = 'X.Y.Z'` |
| `src/__tests__/installer.test.ts` | `expect(VERSION).toBe('X.Y.Z')` |
| `.claude-plugin/plugin.json` | `"version": "X.Y.Z"` |
| `README.md` | Title + version badge |
## Semantic Versioning
- **patch** (X.Y.Z+1): Bug fixes, minor improvements
- **minor** (X.Y+1.0): New features, backward compatible
- **major** (X+1.0.0): Breaking changes
## Notes
- Always run tests before publishing
- Create release notes summarizing changes
- Plugin marketplace syncs automatically from GitHub releases