design-review

Detect dependency and encapsulation smells in module interfaces.

143|52|Updated May 15, 2026
One-click install
npx skills add https://github.com/gotgenes/pi-packages --skill design-review-gotgenes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review
Source: https://github.com/gotgenes/pi-packages/tree/main/.pi/skills/design-review
Command: npx skills add https://github.com/gotgenes/pi-packages --skill design-review-gotgenes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a module's dependency and structural patterns for code smells to guide refactoring decisions and maintainable architecture.

Core Features & Use Cases

  • Detect dependency width and Law of Demeter violations in interfaces and parameter bags.
  • Identify and prevent risky output arguments, scattered resets, and parameter relays.
  • Provide actionable recommendations and guardrails to improve modularity and encapsulation before large-scale changes.

Quick Start

Audit a target module using the built-in checklist to surface design smells, then document findings and suggested fixes.

Frequently Asked Questions about design-review

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

FAQPage Schema
How do I identify dependency width and encapsulation code smells before refactoring?

Identify dependency width and encapsulation code smells by auditing modules with a structured checklist that verifies Law of Demeter violations, output arguments, and parameter relays to guide refactoring decisions.

What is the best way to evaluate Law of Demeter violations in module interfaces?

Evaluate Law of Demeter violations by applying a structured review checklist to module interfaces and parameter bags, checking dependency width and detecting scattered resets to enforce maintainable architecture.

How do I audit test mock depth and scattered resets in my codebase?

Audit test mock depth and scattered resets by applying a design review checklist to test factories and module wiring, verifying intermediate abstractions to improve modularity and encapsulation.

When do I need a design review for modularity and dependency management?

You need a design review for modularity and dependency management when interfaces gain new fields, test factories expand, or wiring across layers becomes complex, requiring an evaluation of dependency smells before large-scale changes.

Can I check for parameter relay and output arguments in related modules without specific testing frameworks?

Yes, you can check for parameter relay and output arguments in related modules without specific testing frameworks by applying a structured design review checklist to verify encapsulation smells and structural patterns.

Why does my module refactoring introduce complex wiring across layers?

Module refactoring introduces complex wiring across layers when dependency width grows and encapsulation smells like parameter relays and intermediate abstractions are not evaluated using a structured review checklist beforehand.