code_review

Spawns an architect subagent for code analysis, planning, and debugging.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/BotchaVarun/EduBot --skill code-review-botchavarun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/BotchaVarun/EduBot/tree/main/.local/skills/code_review
Command: npx skills add https://github.com/BotchaVarun/EduBot --skill code-review-botchavarun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deep architectural analysis, root cause debugging, and implementation planning require focused reasoning that is hard to do alongside active coding. This Skill delegates that work to a dedicated architect subagent that analyzes specified files and returns structured strategic guidance without making code changes. ## Core Features & Use Cases - Architect Subagent: Spawn an analysis-focused subagent with a defined task, relevant files, and a responsibility mode. - Three Responsibility Modes: Use "plan" for implementation planning, "debug" for root cause analysis, and "evaluate_task" for reviewing completed work. - Git Context Integration: Include the current unstaged diff or a commit range (e.g., "HEAD~3..HEAD") so the architect understands recent changes. - Use Case: After building a major feature, ask the architect to evaluate the implementation against design goals, or debug why a session validation function rejects valid tokens. ## Quick Start Ask the architect to review the authentication module files and debug why token validation fails for valid sessions.

Frequently Asked Questions about code_review

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

FAQPage Schema
How do I get an architectural review of my code?▼

Call the architect function with a specific task description, the full paths of relevant files, and the responsibility set to "evaluate_task". The subagent returns a structured analysis with strategic recommendations without modifying any code.

How to debug a regression using a code review subagent?▼

Set the responsibility parameter to "debug", describe the failing behavior with concrete function names or error messages, and enable includeGitDiff. The architect analyzes recent changes to identify the root cause and recommend fixes.

When should I use the architect instead of editing code directly?▼

Use the architect for analysis, planning, and debugging after building major features. It does not perform file edits or implementation; for tasks requiring code changes, use the delegation skill instead.

Can the architect analyze git commit history?▼

Yes, pass a commit range through the relevantGitCommits parameter, such as "HEAD~3..HEAD", to give the architect context on recent history. You can also include the current unstaged diff with includeGitDiff.

What are the limitations of the architect subagent?▼

The architect only analyzes files explicitly passed in relevantFiles and cannot edit code or perform read-only exploration on its own. Simple tasks, direct implementation, and basic file reads should use other tools instead.