/release-bump
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish
$ npx -y skills add mikeyobrien/ralph-orchestrator --skill release-bump --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/release-bump
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish
SKILL.md
release-bump.SKILL.mdname: release-bump
description: Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish
metadata:
internal: true
Release Bump
Overview
Bump version and trigger release for ralph-orchestrator. All versions live in workspace `Cargo.toml` - individual crates inherit via `version.workspace = true`.
Confirm the new version with the user. Once the bump commit is pushed, track progress of the release.
Quick Reference
| Step | Command/Action | |------|----------------| | 1. Bump version | Edit `Cargo.toml`: replace all `version = "X.Y.Z"` (7 occurrences) | | 2. Build | `cargo build` (updates Cargo.lock) | | 3. Test | `cargo test` | | 4. Commit | `git add Cargo.toml Cargo.lock && git commit -m "chore: bump to vX.Y.Z"` | | 5. Push | `git push origin main` | | 6. Tag | `git tag vX.Y.Z && git push origin vX.Y.Z` |
Version Locations (All in Cargo.toml)
# Line ~17 - workspace version
[workspace.package]
version = "X.Y.Z"
# Lines ~113-118 - internal crate dependencies
ralph-proto = { version = "X.Y.Z", path = "crates/ralph-proto" }
ralph-core = { version = "X.Y.Z", path = "crates/ralph-core" }
ralph-adapters = { version = "X.Y.Z", path = "crates/ralph-adapters" }
ralph-tui = { version = "X.Y.Z", path = "crates/ralph-tui" }
ralph-cli = { version = "X.Y.Z", path = "crates/ralph-cli" }
ralph-bench = { version = "X.Y.Z", path = "crates/ralph-bench" }**Tip:** Use Edit tool with `replace_all: true` on `version = "OLD"` → `version = "NEW"` to update all 7 at once.
What CI Does Automatically
Once you push the tag, `.github/workflows/release.yml` triggers and:
1. Creates the GitHub Release with auto-generated notes 2. Builds binaries for macOS (arm64, x64) and Linux (arm64, x64) 3. Uploads artifacts to the GitHub Release 4. Publishes to crates.io (in dependency order) 5. Publishes to npm as `@ralph-orchestrator/ralph`
Common Mistakes
| Mistake | Fix | |---------|-----| | Only updating workspace.package.version | Must update all 7 occurrences including internal deps | | Forgetting to run tests | Always `cargo test` before commit | | Creating release manually with `gh release create` | Just push the tag - CI creates the release with artifacts | | Pushing tag before main | Push main first, then push the tag |
Read more
name: release-bump description: Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish metadata: internal: true
Release Bump
Overview
Bump version and trigger release for ralph-orchestrator. All versions live in workspace `Cargo.toml` - individual crates inherit via `version.workspace = true`.
Confirm the new version with the user. Once the bump commit is pushed, track progress of the release.
Quick Reference
| Step | Command/Action | |------|----------------| | 1. Bump version | Edit `Cargo.toml`: replace all `version = "X.Y.Z"` (7 occurrences) | | 2. Build | `cargo build` (updates Cargo.lock) | | 3. Test | `cargo test` | | 4. Commit | `git add Cargo.toml Cargo.lock && git commit -m "chore: bump to vX.Y.Z"` | | 5. Push | `git push origin main` | | 6. Tag | `git tag vX.Y.Z && git push origin vX.Y.Z` |
Version Locations (All in Cargo.toml)
# Line ~17 - workspace version
[workspace.package]
version = "X.Y.Z"
# Lines ~113-118 - internal crate dependencies
ralph-proto = { version = "X.Y.Z", path = "crates/ralph-proto" }
ralph-core = { version = "X.Y.Z", path = "crates/ralph-core" }
ralph-adapters = { version = "X.Y.Z", path = "crates/ralph-adapters" }
ralph-tui = { version = "X.Y.Z", path = "crates/ralph-tui" }
ralph-cli = { version = "X.Y.Z", path = "crates/ralph-cli" }
ralph-bench = { version = "X.Y.Z", path = "crates/ralph-bench" }**Tip:** Use Edit tool with `replace_all: true` on `version = "OLD"` → `version = "NEW"` to update all 7 at once.
What CI Does Automatically
Once you push the tag, `.github/workflows/release.yml` triggers and:
1. Creates the GitHub Release with auto-generated notes 2. Builds binaries for macOS (arm64, x64) and Linux (arm64, x64) 3. Uploads artifacts to the GitHub Release 4. Publishes to crates.io (in dependency order) 5. Publishes to npm as `@ralph-orchestrator/ralph`
Common Mistakes
| Mistake | Fix | |---------|-----| | Only updating workspace.package.version | Must update all 7 occurrences including internal deps | | Forgetting to run tests | Always `cargo test` before commit | | Creating release manually with `gh release create` | Just push the tag - CI creates the release with artifacts | | Pushing tag before main | Push main first, then push the tag |
A hat-based orchestration framework that keeps AI agents in a loop until the task is done. "Me fail English? That's unpossible!" - Ralph Wiggum
Repo: mikeyobrien/ralph-orchestrator
Other skills on ralph-orchestrator.
- /code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
Open skill - /code-task-generator
Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with Given-When-Then acceptance criteria.
Open skill - /evaluate-presets
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
Open skill - /find-code-tasks
Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
Open skill - /pdd
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Open skill - /playwriter
Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.
Open skill

