Ship for openclaw
Skill LeoYeAI/openclaw-coding-skills/skills/ship-for-openclaw
Production-grade coding workflow, execution scaffolding, and tuning skills for OpenClaw agents, part of the MyClaw.ai ecosystem.
npx -y skills add LeoYeAI/openclaw-coding-skills --skill ship-for-openclawAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Prepare an OpenClaw change for safe handoff or release. Use when the request sounds like "wrap this up", "close this out", "are we ready to ship", "prepare final handoff", or any task where work is complete enough to need a disciplined final pass over diffs, verification, documentation, and rollout risk.
SKILL.md
1.0 KB, as published. Nobody here has run it
Ship For OpenClaw
Finish with discipline.
Process
- Re-read the final diff with accidental change detection in mind.
- Confirm the requested outcome is actually met.
- Confirm verification matches the risk of the change.
- Update docs, prompts, or operational notes if behavior changed.
- Create a focused git commit unless the user said not to.
- Summarize outcome, evidence, and residual risk.
Closeout Rules
- Do not hide unverified areas.
- Do not include unrelated churn in the final diff.
- Do not claim deploy safety without a concrete basis.
- Prefer one coherent commit over a messy pile of saves.