How does the diagnostic funnel work?

It sequences reviews from broad to narrow, starting with complexity triage, followed by structural and interface reviews, and finishing with surface checks and a red-flags sweep.

When should I use the Design Review skill?

Use this skill when you need a comprehensive, prioritized assessment of a file, module, or PR's overall design quality rather than a check for a single specific issue.

Does this skill provide a prioritized list of issues?

Yes, it ranks findings starting with 'Syndrome Clusters' (systemic issues) down to surface-level naming and documentation problems.

What is the 'Deep Modules' check?

It assesses whether a module provides powerful functionality behind a simple interface, helping you avoid 'classitis' and shallow wrappers that increase system complexity.

Can I use this for tracking code history?

No, this skill focuses on current design quality. For evolutionary analysis of how code has changed over time, use the 'code-evolution' skill.

Design Review Orchestrator

Name: Design Review Orchestrator
Author: codybrom

bycodybrom

•

コラボレーションツール

Orchestrates a structured, multi-phase assessment of software design quality and architectural integrity.

The Design Review Orchestrator acts as a high-level diagnostic engine for your codebase, guiding Claude through a rigorous five-phase funnel to identify hidden complexity and architectural flaws. Based on deep engineering principles, it systematically evaluates code from broad structural boundaries down to surface-level naming conventions, providing a prioritized list of findings. It is particularly effective for evaluating Pull Requests or auditing legacy modules, ensuring that complexity is managed and abstractions remain 'deep' rather than shallow or leaky.

主な機能

013 GitHub stars

02Deep module analysis to evaluate abstraction quality and information hiding effectiveness.

03Five-phase diagnostic funnel: Complexity, Structural, Interface, Surface, and Red Flags.

04Prioritized reporting that ranks systemic architectural issues above surface-level naming.

05Early termination logic that stops the review if no actionable findings or red flags are detected.

06Automated complexity triage to identify change amplification and cognitive load symptoms.

ユースケース

01Conducting high-level architectural audits of complex Pull Requests (PRs).

02Identifying root causes of technical debt before a major refactoring effort.

03Ensuring new modules adhere to software design principles like 'pulling complexity down'.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add codybrom/clairvoyance design-review

For use in Claude.ai and ChatGPT

主な機能

013 GitHub stars

02Deep module analysis to evaluate abstraction quality and information hiding effectiveness.

03Five-phase diagnostic funnel: Complexity, Structural, Interface, Surface, and Red Flags.

04Prioritized reporting that ranks systemic architectural issues above surface-level naming.

05Early termination logic that stops the review if no actionable findings or red flags are detected.

06Automated complexity triage to identify change amplification and cognitive load symptoms.

ユースケース

01Conducting high-level architectural audits of complex Pull Requests (PRs).

02Identifying root causes of technical debt before a major refactoring effort.

03Ensuring new modules adhere to software design principles like 'pulling complexity down'.