skills.rest
gao-hongnan
gao-hongnanCOMMUNITY
Explore all skills by this author →
Website𝕏@gaohongnanGitHub

design-review

Analyze source code for maintainability issues and architectural risks.

3|Updated May 12, 2026
Search Tags:#architecture#code review#refactoring#design patterns#maintainability#technical debt
One-click install
npx skills add https://github.com/gao-hongnan/omniagents --skill design-review-gao-hongnan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/gao-hongnan/omniagents/tree/main/plugins/reviewer/skills/design-review
Command: npx skills add https://github.com/gao-hongnan/omniagents --skill design-review-gao-hongnan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of technical debt by identifying design flaws that make future code changes more expensive, risky, or error-prone.

Core Features & Use Cases

  • Next-Change Simulation: Predicts the impact of future requirements to detect change amplification.
  • Pattern Analysis: Detects convention drift, boundary leaks, and speculative abstractions by comparing code against established architectural norms.
  • Use Case: Use this during a pull request to determine if a new abstraction is premature or if a module is violating layering boundaries, ensuring the codebase remains maintainable as it grows.

Quick Start

Invoke the design-review skill on the current diff to identify potential maintainability issues and architectural risks.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I identify maintainability risks and technical debt in my code design?▼

To identify maintainability risks, analyze source code for coupling, cohesion, and design pattern misuse. Evaluating code changes against architectural boundaries and convention consistency prevents accumulating technical debt.

What's the best way to detect architectural boundary leaks and convention drift?▼

Detecting convention drift and boundary leaks is best done through pattern analysis, which compares source code against established architectural norms to identify speculative abstractions and layering violations.

How do I check if a new abstraction is premature or violates layering boundaries?▼

To check if a new abstraction is premature, analyze the code diff during a pull request to evaluate the impact of future requirements, detecting change amplification and architectural boundary violations.

How does predicting future requirements impact prevent technical debt during code review?▼

Predicting future requirements impacts prevents technical debt by simulating the next change to detect change amplification. This proactive evaluation ensures the codebase remains extensible and maintainable as it grows.

Can I analyze code cohesion and coupling issues directly from a pull request diff?▼

You can analyze code cohesion and coupling issues directly from a pull request diff by invoking design review tools that evaluate source code changes against extensibility requirements and architectural boundaries.

When should I not use automated design pattern analysis for refactoring?▼

Automated design pattern analysis for refactoring may not be suitable when the primary goal is fixing functional bugs rather than addressing structural maintainability issues, as it focuses specifically on preventing long-term architectural risks.

Related Skills

Explore More Software Engineering Skills→
SebKaySebKay
1

audit-idiomatic

Audit codebases for non-idiomatic language and framework usage.

Community
Advanced
mgd34msumgd34msu
4

architecture-assessment

Analyze codebase architecture for patterns, anti-patterns, coupling, and technical debt.

Community
Advanced
speednet-softwarespeednet-software
21

code-review-yagni-detector

Flag YAGNI violations in code diffs during code reviews.

Official
Advanced
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced