requesting-code-review

Automate code-review requests using a code-reviewer subagent and git SHAs.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Suara17/guanlan-sina --skill requesting-code-review-suara17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Suara17/guanlan-sina/tree/main/.opencode/skills/requesting-code-review
Command: npx skills add https://github.com/Suara17/guanlan-sina --skill requesting-code-review-suara17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures early, structured code reviews are requested to detect issues before they cascade into bigger problems.

Core Features & Use Cases

  • Automated review prompts: Dispatch a code-reviewer subagent to assess recent changes.
  • Review gate for development cycles: Enforce review after each subagent task, after major feature completion, and before merging to main.
  • Ad-hoc feedback workflow: Capture actionable feedback and guide fixes before moving forward.
  • Use case: After implementing a feature via subagent-driven development, trigger a formal review before merge.

Quick Start

Use the requesting-code-review process to prompt a reviewer for the latest changes before merging.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate code review requests before merging a pull request?

Automate code review requests by dispatching a code-reviewer subagent to assess recent changes before merging to main. The process uses git SHAs for diff context and a predefined template with placeholders to structure feedback on pull requests.

When should I request a code review in a subagent-driven development workflow?

Request a code review after completing each subagent task, finishing major features, and before merging to main branches. This enforces a review gate to catch issues earlier in the software engineering workflow.

How do I structure code review feedback for recent git commits?

Structure code review feedback using a predefined template with placeholders to capture actionable fixes. The review context is generated using git SHAs to diff recent commits and guide fixes before moving forward.

Does automated code review work without manual reviewer intervention?

Automated code review relies on a code-reviewer subagent to evaluate recent changes without manual intervention. It dispatches the review process automatically and returns structured feedback to guide code fixes.

What is the best way to catch code issues early before they cascade?

The best way to catch code issues early is to prompt structured code reviews after major feature completion. Enforcing early review gates detects problems before they cascade into bigger issues during software development.

Can I use git SHAs to provide diff context for pull request reviews?

Yes, you can use git SHAs to provide diff context for pull request reviews. The code-reviewer subagent uses these git SHAs to identify recent changes and apply the predefined feedback template accurately.