Review for openclaw
Skill LeoYeAI/openclaw-coding-skills/skills/review-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 review-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
Critically review a code or prompt change in an OpenClaw workspace before merge or handoff. Use when the request sounds like "review this", "audit this PR", "look for bugs", "sanity-check this implementation", or "tell me what is risky here", especially when regressions, weak assumptions, missing tests, or release risk are concerns.
SKILL.md
1.1 KB, as published. Nobody here has run it
Review For OpenClaw
Review for failure modes first, not presentation quality.
Process
- Identify the claimed intent of the change.
- Compare the implementation against that intent.
- Look for bugs, regressions, risk, and missing coverage.
- Check whether verification is sufficient for the risk level.
- Report findings ordered by severity.
Review Priorities
- behavioral correctness
- edge cases and regressions
- verification gaps
- interface consistency
- maintainability risk
Output Standard
Lead with findings. If there are no findings, say so explicitly and note residual uncertainty.
Reference Files
Read references/finding-template.md when you need a stronger structure for review findings.