code-quality-review

Review code for architecture, code smells, performance, and type-safety issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DaichiHoshina/ai-tools --skill code-quality-review-daichihoshina
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-review
Source: https://github.com/DaichiHoshina/ai-tools/tree/main/claude-code/skills/code-quality-review
Command: npx skills add https://github.com/DaichiHoshina/ai-tools --skill code-quality-review-daichihoshina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates architecture, code smells, performance, and typing checks into a single, unified review workflow to accelerate delivery of high-quality code.

Core Features & Use Cases

  • Integrated viewpoints for architecture, code smells, performance, and type-safety checks without switching tools.
  • Multi-scenario support including code reviews, refactoring, and automated review runs with actionable improvements.
  • Real-world use: evaluate an early PR to surface architectural concerns, smells, and typing issues, guiding fixes before merge.

Quick Start

Run /skill comprehensive-review --focus=quality to perform a full code-quality review.

Frequently Asked Questions about code-quality-review

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

FAQPage Schema
How do I perform a unified code quality review for architecture and type-safety issues?

A unified code quality review consolidates architecture, code smells, performance, and strict typing checks into a single workflow. This process surfaces cross-cutting quality concerns during code reviews and refactoring sessions to accelerate high-quality code delivery.

What is the best way to check TypeScript code smells and performance issues before a merge?

The best way to check TypeScript code smells and performance issues before a merge is applying a structured checklist during an early pull request review. This evaluates architectural concerns, smells, and typing problems to guide fixes before integration.

Can I use an automated review run to identify architectural concerns in my codebase?

Yes, you can use an automated review run to identify architectural concerns. It applies multi-scenario support to evaluate structural quality, surfacing cross-cutting architectural issues and code smells automatically to guide actionable improvements.

Does static analysis for refactoring work with strict typing checks?

Static analysis for refactoring works seamlessly with strict typing checks by consolidating them into an integrated viewpoint. This unified workflow evaluates type-safety alongside code smells and performance optimization without requiring tool switching.

Why use a single code quality review workflow instead of multiple specialized tools?

A single code quality review workflow eliminates the need to switch tools by integrating architecture, code smells, performance, and type-safety checks. This consolidation accelerates delivery by providing a structured checklist that addresses all cross-cutting concerns.