code_review

Spawn an architect subagent to analyze code changes and plan debugging strategies.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gopforever/Idle-Echoes --skill code-review-gopforever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/gopforever/Idle-Echoes/tree/main/.local/skills/code_review
Command: npx skills add https://github.com/gopforever/Idle-Echoes --skill code-review-gopforever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn a code review (architect) subagent for deep analysis, planning, and debugging. The architect specializes in analysis and strategic guidance rather than implementation.

Core Features & Use Cases

  • Architectural analysis and strategic guidance for complex codebases
  • Root-cause debugging, design evaluation, and planning assistance
  • Works with a defined task and relevant files to produce actionable recommendations

Quick Start

Ask the architect to review the current codebase by providing a task and a list of relevant files.

Frequently Asked Questions about code_review

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

FAQPage Schema
How do I get architectural analysis and strategic guidance for complex codebase changes?

To get architectural analysis, spawn a code-review architect subagent by providing a task and relevant files. It evaluates design and provides strategic guidance for complex software changes.

Can I use git history for root-cause debugging and design evaluation?

Yes, you can use git history for root-cause debugging by enabling includeGitDiff and relevantGitCommits inputs. This supports history-aware analysis and troubleshooting during the review.

Does the code review architect write implementation code or only provide analysis?

The code review architect specializes in analysis and strategic guidance rather than implementation. It produces actionable recommendations and planning assistance instead of writing code.

What inputs do I need to start a code review for a specific software engineering task?

To start a code review, you need to provide the task, relevantFiles, and responsibility as inputs. These generate structured analysis results for your software engineering planning.

What's the best way to plan complex software changes and debug architectural issues?

The best way to plan complex software changes is using a code-review architect. It analyzes relevant files and responsibilities to provide structured analysis, design evaluation, and debugging assistance.