Best use case
release is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automated release workflow for oh-my-droid
Teams using release should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/release/SKILL.md --create-dirs "https://raw.githubusercontent.com/MeroZemory/oh-my-droid/main/skills/release/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/release/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How release Compares
| Feature / Agent | release | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automated release workflow for oh-my-droid
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Release Skill
Automate the release process for oh-my-droid.
## Usage
```
/release <version>
```
Example: `/release 2.4.0` or `/release patch` or `/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)
- `.factory-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-droid
- [ ] GitHub: https://github.com/MeroZemory/oh-my-droid/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')` |
| `.factory-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 releasesRelated Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.