Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-saurabh/release-engineer
Structured release and ship workflow skill.
Passed 24 of 24 test cases with the skill, and 19 of 24 without it.
and 6 more in the full report
5 fixed19 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
A bad deployment named 'user-service' in namespace 'backend' is causing production crashes. Show the single kubectl command to immediately undo the deployment and revert to the previous revision.
| Checked | Without skill | With skill |
|---|---|---|
| Uses kubectl rollout undo deployment/user-service -n backend. | Missed | Passed |
The instructions your model reads when the skill loads.
Approach every release as the engineer who owns it end-to-end — from the last line of code to verified traffic in production. A release isn't done when the PR is merged. It's done when the system is healthy, metrics are normal, and you could roll back in under five minutes if they weren't.
Before executing any steps, determine which path applies:
main, standard CI gate, deploy to production on merge.main, fix, fast-track review, deploy, backport.If the user hasn't said which path, ask. Choosing the wrong path (treating a hotfix like a normal release) adds minutes you don't have when production is down. Choosing the wrong path in the other direction (treating a normal feature like a hotfix) bypasses the quality gates that exist for a reason.
State which path you're on at the start of every release workflow, and why.
Run this checklist before touching git for any release. Every item has a reason — don't skip any without documenting why.
git fetch origin
git checkout main && git pull --ff-only origin main
git checkout <your-branch>
git rebase origin/main
# Resolve any conflicts. Rebasing (not merging) keeps history linear and
# makes the diff in the PR exactly what you changed — not mixed with merge noise.
If the rebase surfaces conflicts, resolve them now. A PR with conflicts doesn't merge cleanly and signals to reviewers that the branch is stale.
Run the full local quality suite — don't skip steps because "CI will catch it." CI feedback takes minutes; local feedback takes seconds. A red CI on a PR you just opened is a social and velocity cost.
test cases passed, vs 19 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.