code_review

Analyze codebases to produce architectural guidance, root-cause findings, and implementation plans.

Updated Jun 20, 2026

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

Ready to run

npx skills add https://github.com/4tie/fortiesr --skill code-review-4tie

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reason about complex codebases when you need architectural guidance, root-cause analysis, or a structured plan instead of direct implementation.

Core Features & Use Cases

Deep code understanding: Analyze system design, dependencies, and technical tradeoffs.
Planning support: Break down major features into sequenced implementation steps.
Debugging guidance: Investigate failures, regressions, and likely root causes.
Use case: Ask for a review of a backend service, a rollout plan for a new API, or a diagnosis of a recurring bug.

Quick Start

Use the code_review skill to review the relevant files and produce an architectural analysis of the problem you are investigating.

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 code review and root-cause analysis for a complex codebase?▼

Architectural code review analyzes your selected files and git history to produce system design evaluation, root-cause findings, and structured implementation plans. You provide relevant file paths and optional git diffs to receive architectural guidance and debugging assistance.

What's the best way to break down a major feature into sequenced implementation steps?▼

Feature planning breaks down major features into sequenced implementation steps by evaluating your codebase architecture and technical tradeoffs. Using responsibility modes like plan, you receive structured rollout guidance for new APIs or backend services.

Can I diagnose a recurring bug or regression using git commit ranges?▼

Debugging guidance investigates failures and regressions by analyzing git commit ranges and selected file paths. This root-cause analysis identifies likely causes of recurring bugs across your codebase without requiring direct implementation changes.

How do I assess technical debt and system design dependencies in my backend service?▼

Technical debt assessment evaluates system design dependencies and technical tradeoffs by analyzing your selected files. This deep code understanding reveals architectural weaknesses and provides actionable guidance for reducing accumulated technical debt.

Do I need to provide specific file paths to get a code review?▼

Yes, relevant file paths are required to perform a code review, along with optional git diffs or commit ranges. The analysis applies responsibility modes for plan, debug, or evaluate_task to produce the appropriate architectural guidance.

Why does my code review output a plan instead of implementation code?▼

Code review produces architectural guidance, root-cause findings, and implementation plans rather than direct implementation. This approach helps you reason about complex codebases by providing structured analysis and technical tradeoff evaluation instead of writing code.