openclaw-review

Orchestrate L2 diff review workflows for L3 code changes on staging branches.

Updated Feb 18, 2026

Search Tags:#git #workflow #code review #staging branch #l3 specialist #l2 review

Ready to run

npx skills add https://github.com/ollieb89/openrepo --skill openclaw-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-review
Source: https://github.com/ollieb89/openrepo/tree/main/skills/openclaw-review
Command: npx skills add https://github.com/ollieb89/openrepo --skill openclaw-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process for L2 agents to review code changes submitted by L3 specialists on staging branches, ensuring code quality and adherence to project standards before merging.

Core Features & Use Cases

Diff Review: Enables L2 agents to capture snapshots of L3 work, manually review code differences, and validate against a checklist.
Decision Making: Facilitates clear "approve" or "reject" decisions for L3 tasks.
State Management: Updates task statuses to "completed" or "rejected" based on review outcomes.
Use Case: After an L3 specialist completes a coding task, the L2 Project Manager uses this skill to review the submitted code diff, verify it meets requirements, and then merge it into the main branch or reject it with specific feedback.

Quick Start

Use the openclaw-review skill to review the L3 work on the 'l3/task-abc123' branch.

Frequently Asked Questions about openclaw-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review code changes on a staging branch before merging?▼

To review code changes on a staging branch, you can capture a snapshot of the work, manually validate the code diff against a checklist, and then make a decision to merge or reject the task. This ensures code quality before integration.

What is the best way to manage task state after a code review?▼

Managing task state after a code review involves updating the task status in the state engine to either "completed" for approved changes or "rejected" for unapproved work, ensuring the system tracks the outcome of the diff validation.

How do I capture a snapshot of specialist code changes for manual diff validation?▼

Capturing a snapshot of specialist code changes requires using git branch operations to isolate the submitted work, allowing an L2 agent to manually review the differences and verify them against project standards before merging.

Does the code review workflow require integration with git for branch operations?▼

Yes, the code review workflow requires integration with git for branch operations to manage staging branches, and it also connects to a state engine to update task statuses accurately based on review outcomes.

When should I reject a specialist task instead of merging it into the main branch?▼

You should reject a specialist task instead of merging when the manual diff validation identifies failures in meeting project requirements, triggering a rejected status in the state engine to provide specific feedback for revisions.

Can I use this to orchestrate an L2 diff review for L3 specialist changes?▼

Yes, you can use this to orchestrate an L2 diff review for L3 specialist changes, managing the workflow from capturing code snapshots on staging branches to making the final decision to merge or reject the submitted work.