requesting-code-review

Request code reviews for committed Git ranges using the OpenCode task tool.

34|6|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Chikage0o0/opencode --skill requesting-code-review-chikage0o0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Chikage0o0/opencode/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/Chikage0o0/opencode --skill requesting-code-review-chikage0o0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures that major features and pre‑merge code are thoroughly examined for quality, compliance, and risk, preventing defects from reaching production.

Core Features & Use Cases

  • Automated review dispatch: Uses the OpenCode task tool to launch a code‑reviewer subagent with a structured prompt.
  • Committed‑range support: Handles reviews for specific Git SHAs, enabling precise diff analysis.
  • Guided feedback workflow: Categorizes findings (Critical, Important, Minor) and defines actions for each.

Quick Start

Ask the assistant to request a code review 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 for a specific Git diff range before merging?

You can automate code review by dispatching a reviewer subagent with a structured prompt. It analyzes a specific Git diff range defined by base and head SHAs to identify defects before merging.

How do I request a code review for my committed feature branch?

To request a code review, specify base and head SHAs, review goals, context, and diff range. This dispatches a guided task to examine the committed changes and categorize findings.

Can I target a specific Git commit range for automated code review?

Yes, you can target specific Git commit ranges for automated code review. The process requires specifying the base and head SHAs to enable precise diff analysis on committed changes.

How does the automated code review workflow categorize feedback?

The automated code review workflow categorizes feedback into Critical, Important, and Minor findings. It defines specific actions for each category to ensure quality and compliance before merging.

What context do I need to provide for a targeted Git diff review?

For a targeted Git diff review, you need to provide base and head SHAs, review goals, context, and the diff range. This structured input ensures the reviewer subagent properly examines the changes.