solid-principles

Analyze object-oriented source code for SOLID principle violations with severity ratings and refactoring suggestions.

12|1|Updated Feb 9, 2026

Search Tags:#code quality #architecture #refactoring #design patterns #solid principles #object-oriented design

Ready to run

npx skills add https://github.com/florianbuetow/claude-code --skill solid-principles-florianbuetow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solid-principles
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/solid-principles/skills/solid-principles
Command: npx skills add https://github.com/florianbuetow/claude-code --skill solid-principles-florianbuetow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix violations of the SOLID principles in their object-oriented code, leading to more maintainable, flexible, and robust software.

Core Features & Use Cases

Automated Auditing: Analyzes code for violations of all five SOLID principles (SRP, OCP, LSP, ISP, DIP).
Targeted Checks: Allows focusing on specific principles or running a full audit.
Actionable Feedback: Provides severity ratings and concrete refactoring suggestions for each violation.
Use Case: A developer suspects their class is becoming a "god object" and wants to check for SRP violations. They use this Skill to get a detailed report with specific recommendations on how to refactor.

Quick Start

Use the solid-principles skill to check for SOLID violations in the attached file 'my_class.py'.

Frequently Asked Questions about solid-principles

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

FAQPage Schema

How do I check my object-oriented code for SOLID design principle violations?▼

To check object-oriented code for SOLID design principle violations, you can audit the source file directly. This process analyzes the code against all five principles, identifies specific flaws, and provides severity ratings with refactoring suggestions to improve maintainability.

What is the best way to refactor a god object that violates the Single Responsibility Principle?▼

The best way to refactor a god object violating the Single Responsibility Principle is to run a targeted audit. This identifies specific SRP violations and provides concrete refactoring suggestions to split the class into smaller, maintainable components.

Can I audit my source code for just one specific SOLID principle instead of all five?▼

Yes, you can audit source code for just one specific SOLID principle instead of all five. The analysis supports targeted checks, allowing you to focus exclusively on Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, or Dependency Inversion.

How does an automated audit detect Liskov Substitution and Interface Segregation issues?▼

An automated audit detects Liskov Substitution and Interface Segregation issues by analyzing the object-oriented source code structure. It identifies specific design flaws where subclasses break parent contracts or where classes are forced to implement unused methods.

Does this SOLID principles audit work with any object-oriented programming language?▼

The SOLID principles audit analyzes object-oriented source code regardless of the specific programming language. By evaluating the code structure against the five design principles, it provides actionable feedback and refactoring suggestions for any object-oriented codebase.

When should I run a full SOLID design audit versus a targeted check?▼

You should run a full SOLID design audit when assessing overall code quality and architecture, but use a targeted check when you suspect a specific issue like a god object. Both approaches yield severity ratings and refactoring suggestions for the identified violations.