codeprobe-solid

Standalone Mode

If invoked directly (not via the orchestrator), you must first:

1. Read ../codeprobe/shared-preamble.md (resolve relative to this SKILL.md's location — the sibling codeprobe skill directory — not the user's project) for the output contract, execution modes, and constraints.
2. Load applicable reference files from ../codeprobe/references/ (same resolution) based on the project's tech stack.
3. Default to full mode unless the user specifies otherwise.

SOLID Principles Auditor

Domain Scope

This sub-skill detects violations of the five SOLID principles:

1. Single Responsibility Principle (SRP) — A class or module should have only one reason to change.
2. Open/Closed Principle (OCP) — Software entities should be open for extension but closed for modification.
3. Liskov Substitution Principle (LSP) — Subtypes must be substitutable for their base types without altering program correctness.
4. Interface Segregation Principle (ISP) — Clients should not be forced to depend on interfaces they do not use.
5. Dependency Inversion Principle (DIP) — High-level modules should not depend on low-level modules; both should depend on abstractions.

---

What It Does NOT Flag

• Simple DTOs/value objects with multiple fields — having many properties is not an SRP violation when the class represents a single data concept.
• Small scripts and CLIs that don't need dependency injection — proportional design matters.
• Enums used in switches where the enum is stable and closed (e.g., compass directions, days of the week) — OCP applies when variants are likely to grow.
• Framework-generated classes following framework conventions (e.g., Laravel migrations, Django admin classes, Rails ActiveRecord models with standard callbacks).
• Test helper classes that aggregate setup utilities — test infrastructure has different design constraints.

---

Detection Instructions

SRP — Single Responsibility Principle

ID Prefix	Signal	How to Detect	Severity
SRP	Class has 5+ public methods doing unrelated things	Count public methods. If 5+ exist, check whether they cluster around a single responsibility or span multiple concerns (e.g., authentication + email + database). Look for method name prefixes that suggest different domains.	Major
SRP	Method exceeds 30 LOC doing multiple concerns	Count lines in each method (excluding blank lines and comments). If > 30 LOC, check whether the method handles multiple distinct steps (validation, transformation, persistence, notification) that could be extracted.	Minor
SRP	Class name is vague	Flag classes named Manager, Handler, Utils, Helper, Processor, Service (when not domain-qualified) — these names suggest the class has no clear single purpose. Exception: if the class is small (< 5 methods, < 100 LOC), downgrade to suggestion.	Minor
SRP	Constructor takes 5+ dependencies	Count constructor parameters or injected dependencies. 5+ dependencies suggest the class has too many responsibilities. Check whether dependencies serve different domains.	Major