القائمة
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
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.
Introspect, explain, and improve Ralph Orchestrator using its published llms.txt doc map. Use this skill whenever the user asks questions about Ralph's behavior, wants to understand how a Ralph internal works (event loop, hats, memories, tasks, backends, presets), debug an unfamiliar failure mode, or propose a code change to the ralph-orchestrator repo. The skill teaches the agent to discover authoritative answers from the live docs via llms.txt before guessing, and to scope improvements through the published architecture rather than the local checkout alone.
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
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.
| 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} |
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.
| 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 |
# 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.
Once you push the tag, .github/workflows/release.yml triggers and:
@ralph-orchestrator/ralph| 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 |