requesting-code-review

What This Skill Does

The requesting-code-review skill acts as a formal bridge between your development work and the code-reviewer subagent. It enforces quality assurance by standardizing the review process, ensuring that every significant unit of work—whether it's a specific task, a major feature, or a final merge—undergoes automated scrutiny. By leveraging the superpowers:code-reviewer subagent, it helps developers identify logic errors, architectural flaws, and stylistic inconsistencies before they cascade into larger technical debt. It promotes a 'review early, review often' philosophy that drastically reduces debugging time later in the development lifecycle.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/zlc000190/requesting-code-review

Ensure your workspace has the necessary permissions for the subagent to access your git history and local filesystem to read the diffs between SHAs.

Use Cases

This skill is essential for:

• Subagent-Driven Development: Triggering a mandatory review after every task completion to ensure modular code integrity.
• Major Feature Implementation: Validating complex logic or structural changes before they are integrated into the main branch.
• Complex Debugging: Providing an objective, automated second set of eyes on difficult-to-trace bugs to verify your proposed fix.
• Refactoring Baseline Checks: Establishing a checkpoint before performing large-scale code restructures to ensure you have a clean starting point.

Example Prompts

1. "I've just finished the authentication module for Task 4. Please run the requesting-code-review flow to check my implementation against the requirements."
2. "I am planning to merge the current branch into main. Use the requesting-code-review skill to verify that I have addressed all pending important feedback."
3. "I'm feeling stuck on the database migration script. Can you dispatch a code-reviewer to look at my current diff and provide a fresh perspective?"

Tips & Limitations

• Be Specific: Always provide clear, accurate descriptions in your template. The quality of the reviewer's output depends heavily on the context provided in your {PLAN_OR_REQUIREMENTS} placeholder.
• Don't Skip: Resist the urge to skip reviews for 'simple' changes; these are often where subtle bugs hide.
• Active Resolution: This skill is not passive. You must actively manage the reviewer's feedback, addressing all 'Critical' and 'Important' issues immediately. If you disagree with the reviewer, provide technical justification rather than ignoring the output.
• Git Hygiene: Ensure your local repository is up to date and your SHAs are correct before dispatching, as the subagent relies on valid git references to generate accurate diffs.