requesting-code-review

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill requesting-code-review-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/requesting-code-review
Command: npx skills add https://github.com/Viranya2006/Lumen --skill requesting-code-review-viranya2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code often ships with undetected bugs, plan deviations, and quality gaps because self-review is unreliable and inline diff review consumes the coordinator's context window. This Skill structures the review process by dispatching a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a structured prompt template covering plan alignment, code quality, architecture, testing, and production readiness. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor issues with file:line references, plus a clear merge readiness verdict. - Read-Only Review Safety: Instructs the reviewer to inspect git history without mutating the working tree, index, or HEAD. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer with the plan reference, receive categorized feedback, fix Critical and Important issues, and only then proceed to the next task or merge. ## Quick Start Ask the assistant 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 requesting-code-review

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

FAQPage Schema
How do I request a code review for completed work?

Capture the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer template. Fill in the description, plan or requirements, and both SHAs so the reviewer can inspect 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.

What does the code reviewer subagent check?

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness. It returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a merge readiness verdict.

Can the reviewer subagent modify my working tree?

No. The template enforces a read-only review: the reviewer must not mutate the working tree, index, HEAD, or branch state. It uses git show, git diff, and git log, or a separate temporary worktree for inspecting other revisions.

What should I do if I disagree with the reviewer's feedback?

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification. Fix Critical issues immediately and Important issues before proceeding.