code_review

Spawn an architect subagent for deep code analysis and strategic planning.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/soq123/SE3354-Calo-fit --skill code-review-soq123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/soq123/SE3354-Calo-fit/tree/main/.local/skills/code_review
Command: npx skills add https://github.com/soq123/SE3354-Calo-fit --skill code-review-soq123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn an architect subagent for deep code analysis, architectural planning, and debugging guidance, focusing on strategy rather than implementation.

Core Features & Use Cases

  • Analyzes code structure, dependencies, and quality to identify architectural improvements.
  • Plans high-level design changes, system patterns, and debt reduction strategies.
  • Assists in root-cause analysis and debugging with actionable, strategic recommendations.

Quick Start

Ask the architect to analyze the current module and produce a high-level refactoring plan for the authentication flow.

Frequently Asked Questions about code_review

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

FAQPage Schema
What is architectural code analysis and when do I need it?

Architectural code analysis evaluates code structure, dependencies, and quality to identify improvements. You need it for design reviews, debt reduction strategies, and root-cause debugging when you require strategic guidance rather than line-level implementation details.

How do I plan high-level design changes for an authentication flow?

Plan high-level design changes by spawning a dedicated architect subagent to analyze the authentication module and produce a structured refactoring plan. This ensures clear responsibilities, task decomposition, and strategic system pattern recommendations.

Can I use this for root-cause analysis and debugging across multiple services?

Yes, root-cause analysis and debugging across modules and services are supported. The architect subagent provides actionable, strategic recommendations to resolve underlying structural issues rather than just patching isolated symptoms.

What is the best way to reduce technical debt across existing modules?

The best way to reduce technical debt is through strategic architectural planning. Analyze code structure and dependencies to identify bottlenecks, then apply structured task decomposition to produce clear, actionable debt reduction strategies.

Does this approach provide implementation code or strategic guidance?

This approach provides strategic guidance, focusing on high-level design changes and architectural planning. It evaluates system patterns and delivers structured outputs for task decomposition instead of writing the actual implementation code.