code_review

Deep architectural analysis is performed by spawning an analysis-focused subagent that evaluates code quality and system design decisions. This approach structures the review by delegating tasks like root-cause debugging and technical debt assessment across relevant files.

Yes, a subagent supports root-cause debugging by analyzing architecture and system design decisions. It processes defined inputs including the specific task, relevant files, and component responsibilities to isolate underlying structural issues.

Automating strategic code review involves spawning an architect-like subagent to verify architecture after feature completion. This delegates the evaluation workflow, analyzing code quality and proposing structural improvements based on defined file inputs.

Yes, specifying relevant files is required to start an automated code review. The subagent workflow relies on clearly defined inputs, specifically the target task, relevant files, and the responsibility scope, to accurately guide planning and evaluate the architecture.

An architect subagent is needed when planning and debugging require structured task delegation across large codebases. It applies to deep architectural analysis, system design decisions, and verifying that implemented features align with the intended structural strategy.

A code review subagent handles technical debt assessment by analyzing system design decisions and code quality across relevant files. It acts as an architect-like entity to evaluate the current architecture and propose targeted structural improvements.