codeprobe-solid

Detect SOLID principle violations in multi-language codebases and generate fix prompts.

4|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-solid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codeprobe-solid
Source: https://github.com/nishilbhave/codeprobe/tree/main/skills/codeprobe-solid
Command: npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-solid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and report SOLID principle violations in codebases, guiding targeted refactoring to improve maintainability and design quality.

Core Features & Use Cases

  • Detect SRP, OCP, LSP, ISP, and DIP violations in classes and modules.
  • Generate concrete fix prompts and guidance to restore clean architecture.
  • Apply to multi-language repositories and diverse codebases, highlighting risky hotspots for refactoring.

Quick Start

Run the SOLID auditor on your codebase to identify principle violations and generate concrete fix prompts.

Frequently Asked Questions about codeprobe-solid

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

FAQPage Schema
How do I detect SOLID principle violations in my codebase?

To detect SOLID principle violations, you can audit your classes, interfaces, and modules for SRP, OCP, LSP, ISP, and DIP infractions. This generates structured findings with severity levels to guide targeted refactoring.

What is the best way to find Single Responsibility Principle violations for refactoring?

Finding Single Responsibility Principle violations involves analyzing classes and modules to identify components with multiple responsibilities. The audit generates structured findings highlighting risky hotspots and provides actionable fix prompts.

Can I run a SOLID audit on a multi-language repository?

Yes, you can run a SOLID audit on a multi-language repository. The analysis applies to diverse codebases and software engineering workflows, identifying design debt across different languages and platforms.

How do I generate actionable fix prompts for SOLID design debt?

To generate actionable fix prompts for SOLID design debt, audit the codebase to identify principle violations. The resulting structured findings include severity levels and targeted guidance to restore clean architecture.

Does static analysis for SOLID principles work for LSP and ISP violations?

Static analysis for SOLID principles effectively detects LSP and ISP violations by examining class hierarchies and interface implementations. It reports these infractions with severity levels to guide targeted refactoring efforts.

When should I run a SOLID code review to identify architecture violations?

You should run a SOLID code review when maintainability drops or design debt accumulates. Auditing identifies SRP, OCP, LSP, ISP, and DIP violations, highlighting risky hotspots that require immediate refactoring.