code_review

Name: code_review
Availability: InStock
Author: khaledmkhaled

Spawn an architect subagent to analyze codebases and return structured analysis.

Updated Dec 10, 2025

Search Tags:#planning #architecture #code review #debugging #technical debt #subagent #git diff

Ready to run

npx skills add https://github.com/KhaledMKhaled/FodaStore --skill code-review-khaledmkhaled

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code_review
Source: https://github.com/KhaledMKhaled/FodaStore/tree/main/.local/skills/code_review
Command: npx skills add https://github.com/KhaledMKhaled/FodaStore --skill code-review-khaledmkhaled

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams analyze complex codebases to produce strategic architectural guidance, identify root causes of issues, and plan next steps without diving into implementation details.

Core Features & Use Cases

Deep architectural analysis: Evaluate code structure, design patterns, and technical debt to guide strategic decisions.
Debug-focused reasoning: Perform root cause analysis and recommend fixes when behavior regresses or breaks.
Planning and decomposition: Produce implementation-oriented plans and sequencing after major features are in place.

Quick Start

Use the code_review skill to ask an architect to analyze and plan how to improve the system design for a failing module, providing the specific files you want reviewed.

Frequently Asked Questions about code_review

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

FAQPage Schema

How do I analyze technical debt and system architecture across my codebase?▼

To analyze technical debt and system architecture, you provide a task and relevant project files to receive structured, architecture-level reasoning. This process evaluates code structure and design patterns to guide strategic decisions without requiring implementation details.

What is the best way to plan system improvements for a failing module?▼

Planning system improvements for a failing module involves providing the specific files and a task description to an architect-style analysis. This generates implementation-oriented plans and sequencing steps to resolve the regression and improve the system design.

How does root cause analysis work when debugging a codebase regression?▼

Root cause analysis for debugging a codebase regression works by evaluating selected files and optional git diffs to identify why behavior breaks. It performs architecture-level reasoning to recommend targeted fixes and strategic next steps for the failing module.

Can I use git diffs and commit ranges to evaluate code structure during a review?▼

Yes, you can include git diffs and commit ranges alongside your task and relevant files to evaluate code structure. This provides the context needed to produce strategic architectural guidance and identify technical debt introduced by recent changes.

Do I need to provide specific files to get architectural guidance for my code?▼

Yes, providing relevant files is required to get architectural guidance for your code. The analysis depends on evaluating the selected files and your defined task to return structured results with strategic recommendations.

Why does architectural analysis require an architect subagent to evaluate code patterns?▼

Architectural analysis requires an architect subagent to evaluate code patterns because it provides deep, strategic reasoning over your selected files. This mechanism ensures the system design and technical debt are evaluated at an architecture level rather than focusing on line-by-line implementation.