Automated release workflow for oh-my-claudecode
63
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/release/SKILL.mdAutomate the release process for oh-my-claudecode.
/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
Execute these steps in order:
Update version in all locations:
package.jsonsrc/installer/index.ts (VERSION constant)src/__tests__/installer.test.ts (expected version).claude-plugin/plugin.json.claude-plugin/marketplace.json (both plugins[0].version and root version)docs/CLAUDE.md (<!-- OMC:VERSION:X.Y.Z --> marker)README.md (version badge and title)npm run test:runAll 231+ tests must pass before proceeding.
git add -A
git commit -m "chore: Bump version to <version>"git tag v<version>
git push origin main
git push origin v<version>npm publish --access publicgh release create v<version> --title "v<version> - <title>" --notes "<release notes>"| 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" |
.claude-plugin/marketplace.json | plugins[0].version + root version |
docs/CLAUDE.md | <!-- OMC:VERSION:X.Y.Z --> |
README.md | Title + version badge |
48ffaac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.