Review and Protect Pull Requests
Developer & Ops
Review
Scan
Gate
Run automated reviews on every PR to flag security problems, risky diffs, and missing tests. The idea is to have a second pair of eyes that never gets tired and catches the things humans skip when reviewing fast.
Useful for
- You merge PRs without a thorough review because your team is small and busy
- You worry about accidentally shipping a hardcoded secret or a broken dependency
- You want consistent code review standards across your whole codebase
Suggested Skills
Pick skills from the phases below based on what you need. Each phase has an example prompt you can copy and try with your agent.
Review skills analyze diffs for bugs, style issues, and logic problems. Scan skills check for secrets, vulnerabilities, and risky changes. Gate skills generate risk scores and merge recommendations.
Review
Analyze code changes for bugs and quality issues.
try in your OpenClaw assistant
Review the diff in my current pull request and flag any logic errors, missing edge cases, or code that does not follow our project conventions.
First review and use these skills:
https://clawskills.sh/skills/ziad-hsn-critical-code-reviewer
Scan
Check for secrets, vulnerabilities, and risky patterns.
try in your OpenClaw assistant
Scan my pull request for any hardcoded secrets, exposed API keys, or known security vulnerabilities in the dependencies I changed.
Gate
Score risk and decide if it is safe to merge.
try in your OpenClaw assistant
Generate a pre-ship risk report for my current branch compared to main, and tell me if it is safe to merge.