code-quality

Enforce SOLID principles and clean code practices during development and refactoring.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/veelenga/dotfiles --skill code-quality-veelenga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/veelenga/dotfiles/tree/main/.claude/skills/code-quality
Command: npx skills add https://github.com/veelenga/dotfiles --skill code-quality-veelenga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces clean code practices such as SOLID principles, readability, and maintainability to reduce technical debt and improve long-term software quality.

Core Features & Use Cases

  • Enforces SOLID principles (SRP, OCP, LSP, ISP, DIP) and promotes best practices like using named constants over magic numbers and strings.
  • Improves code organization, naming clarity, and testability, guiding feature development and refactors toward maintainable design.
  • Use case: during feature development or refactoring, apply the guidelines to validate design decisions, boundaries, and naming to ensure sustainable code.

Quick Start

Provide a concise code-review checklist for a single module to assess SOLID adherence, readability, and maintainability.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I check if my code follows SOLID principles during a refactor?

You can check SOLID adherence by applying code quality guidelines to validate design decisions, module boundaries, and naming clarity, ensuring maintainable software design during refactoring.

What is the best way to reduce technical debt and improve code maintainability?

Reducing technical debt involves enforcing clean code practices like SOLID principles, readable naming, and replacing magic numbers with named constants across your codebase.

How do I enforce clean code organization and testability in feature development?

You can enforce clean code organization and testability by applying guidelines that address SOLID adherence, constant usage over magic numbers, and the avoidance of common anti-patterns.

When should I review code for anti-patterns and readability issues?

Review code for anti-patterns and readability during feature development, refactoring, and architectural changes to validate design decisions and ensure sustainable, maintainable code.

Can I use a code quality checklist for architectural changes across an existing codebase?

Yes, you can apply code quality guidelines to architectural changes across existing codebases to enforce SOLID principles, improve testability, and guide refactoring toward maintainable design.