code-review

Analyze codebases for architecture, quality, and technical debt.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/not-subhu/screech --skill code-review-not-subhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/not-subhu/screech/tree/main/.local/skills/code-review
Command: npx skills add https://github.com/not-subhu/screech --skill code-review-not-subhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides deep architectural analysis, strategic guidance, and debugging assistance for code, making it easier to understand and optimize system design and address technical challenges.

Core Features & Use Cases

  • Deep Analysis: Analyze code for architecture, quality, and technical debt.
  • Strategic Guidance: Offer recommendations on system design and patterns.
  • Debugging: Help identify root causes of issues and suggest fixes.
  • Use Case: After building major features, use this Skill to review the code for any potential issues or areas for improvement.

Quick Start

Run the code-review skill on your latest feature implementation using the command: code-review analyze my_feature.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform an architectural analysis on my codebase?

Architectural analysis examines your codebase to evaluate system design, code quality, and technical debt. It provides strategic guidance for optimizing software structure and identifying root causes of complex issues.

What is the best way to review system design and debug code after building a feature?

Reviewing system design and debugging code post-feature requires deep architectural analysis to identify potential issues and areas for improvement. It targets root causes and offers strategic guidance for code optimization.

Can I use this approach for root cause analysis of technical debt?

Yes, root cause analysis of technical debt is a primary use case for deep architectural code review. It identifies underlying structural flaws causing the debt and suggests fixes to improve code quality.

How does deep code review help with debugging and code quality optimization?

Deep code review helps with debugging by identifying root causes of system issues and suggesting fixes. It optimizes code quality by analyzing technical debt and providing strategic guidance on system design patterns.

Do I need to provide context when running a code review for system design?

Yes, you need to provide appropriate context and configuration for detailed code review analysis. Supplying correct context ensures the architectural analysis accurately targets your system design and debugging requirements.