skills.rest
codybrom
codybromCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

design-review

Review software designs to identify and prioritize complexity and quality problems.

11|Updated Feb 25, 2026
Search Tags:#code review#refactoring#software architecture#complexity analysis#design review#design smells
One-click install
npx skills add https://github.com/codybrom/clairvoyance --skill design-review-codybrom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/codybrom/clairvoyance/tree/main/skills/design-review
Command: npx skills add https://github.com/codybrom/clairvoyance --skill design-review-codybrom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents design issues from becoming expensive maintenance problems by providing a structured, comprehensive review of code, modules, or pull requests.

Core Features & Use Cases

  • Diagnostic Funnel: Progresses from complexity triage through structural, interface, surface, and red-flags reviews.
  • Prioritized Findings: Groups related problems into syndrome clusters and ranks boundary, canary, structural, and surface issues.
  • Scalable Reviews: Supports pipeline-based workflows for large codebases, including adversarial verification of design findings.
  • Use Case: Review a pull request to identify complexity hotspots, information leaks, shallow modules, weak abstractions, naming problems, and unexamined alternatives before they become entrenched.

Quick Start

Use the design-review skill to perform a comprehensive, prioritized design assessment of the specified file, module, or pull request.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I identify and prioritize software design problems in a codebase?▼

Software design problems are identified and prioritized by applying sequential design lenses to detect complexity hotspots, information leaks, and shallow modules, grouping related issues into syndrome clusters for structured triage.

What is the best way to perform a design review on a pull request?▼

A pull request design review progresses through a diagnostic funnel from complexity triage to structural, interface, surface, and red-flags analysis, prioritizing boundary, canary, and structural issues before they become entrenched.

Can I use a design review workflow for large codebase architecture analysis?▼

Large codebase architecture analysis is supported through scalable, pipeline-based workflows that include optional adversarial verification of design findings using repository inspection to ensure comprehensive coverage.

Does code refactoring require a complexity analysis to find design smells?▼

Complexity analysis is essential for finding design smells because it verifies unexamined alternatives, weak abstractions, and structural red flags, preventing design issues from becoming expensive maintenance problems.

When should I not use a comprehensive software architecture review?▼

Comprehensive software architecture reviews should be avoided when early termination criteria are met during initial complexity triage, indicating no significant design-quality problems require deep structural or interface evaluation.

Related Skills

Explore More Software Engineering Skills→
bahayonghangbahayonghang
16

code-quality-review

Review source code for maintainability, abstraction quality, and branching complexity.

Community
Advanced
aurabxaurabx
3

automatic-refactoring

Apply systematic refactoring techniques to reduce code complexity and technical debt.

Official
Intermediate
ripgraphicsripgraphics

code-review

Review code across architecture, quality, security, performance, testing, and documentation.

Community
Advanced
atilladenizatilladeniz
371

software-design-review

Analyze codebases for unnecessary complexity and design problems.

Community
Advanced