think-review-ask

Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/ehadziabdic/WAgents --skill think-review-ask-ehadziabdic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: think-review-ask
Source: https://github.com/ehadziabdic/WAgents/tree/main/opencode/skills/think-review-ask
Command: npx skills add https://github.com/ehadziabdic/WAgents --skill think-review-ask-ehadziabdic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When completing tasks or implementing features, self-reviewing your own code often misses issues and burns context. This Skill dispatches a dedicated code reviewer subagent with precisely crafted context to catch Critical, Important, and Minor issues before they cascade into more work. ## Core Features & Use Cases - Structured Review Dispatch: Provides a complete reviewer prompt template covering plan alignment, code quality, architecture, testing, and production readiness. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, or Minor with file:line references and a clear merge verdict. - Read-Only Safety: The reviewer is explicitly forbidden from mutating the working tree, HEAD, or branch state, and from spawning its own subagents. - Use Case: After finishing a task in subagent-driven development, capture the base and head git SHAs, dispatch the reviewer with the template, fix Critical and Important issues, then proceed to the next task or merge. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before merging.

Frequently Asked Questions about think-review-ask

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

FAQPage Schema
How do I request a code review with a subagent?▼

Get the base and head git SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, plan or requirements, and both SHAs so the reviewer evaluates the exact diff range.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring as a baseline check, or after fixing a complex bug.

Can the code reviewer subagent modify my working tree?▼

No. The review is strictly read-only on the checkout. The reviewer uses git show, git diff, and git log to inspect history, and must use a separate temporary worktree if it needs a different revision.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning rather than accepting invalid feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer on the disputed point.

What are the limitations of subagent-based code review?▼

The reviewer only sees the crafted context and diff range you provide, not your session history, so incomplete requirements can lead to misaligned feedback. It also cannot run or modify code, limiting it to static inspection.