review-codebase

Analyze codebase architecture and design to produce a structured diagnostic report.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-codebase-nesnilnehc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-codebase
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/review-codebase
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill review-codebase-nesnilnehc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes the architecture and design of a given scope (files, directories, or repository root) to produce a structured diagnostic report on boundaries, patterns, tech debt, and overall quality.

Core Features & Use Cases

  • Architectural and design assessment across the specified path to identify boundaries, responsibilities, and coupling.
  • Evaluation of design patterns, code quality, and cross-module dependencies; outputs a structured report with actionable recommendations.
  • Use cases include new modules for architecture reviews, legacy audits, and targeted sampling or teaching scenarios.

Quick Start

Provide the path(s) to analyze (file, directory, or repo root) and I will generate a structured codebase review with actionable improvements.

Frequently Asked Questions about review-codebase

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

FAQPage Schema
How do I perform an architectural code review on a large repository?

An architectural code review analyzes your repository path to evaluate boundaries, responsibilities, and coupling. It generates a structured diagnostic report highlighting design patterns, tech debt, and actionable improvements.

What is the best way to analyze technical debt and cross-module dependencies?

Analyzing technical debt and cross-module dependencies involves evaluating your codebase structure to identify coupling and design flaws. This produces per-module findings with file:line references for precise, actionable guidance.

Can I review the architecture of a specific directory instead of the whole codebase?

Yes, you can review specific directories or files. The analysis accepts targeted paths for new modules, legacy audits, or sampling reviews, providing focused architectural assessments rather than requiring full repository scans.

How do I audit legacy code for design patterns and quality assessment?

Auditing legacy code for design patterns evaluates the current state of your files to identify architectural boundaries and quality issues. It outputs a structured report with per-file findings and actionable recommendations.

Does this codebase analysis evaluate recent git diffs or the current state?

This codebase analysis evaluates the current state of the files rather than git diffs. It assesses existing architecture, design patterns, and technical debt to provide a comprehensive structural diagnostic.