clean-code-principles

Enforce clean-code naming, structure, and error-handling rules during code reviews.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill clean-code-principles-sergeumatyasov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code-principles
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/clean-code-principles
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill clean-code-principles-sergeumatyasov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean-code guidelines that standardize naming, structure, and practices to improve readability, maintainability, and reliability across the codebase.

Core Features & Use Cases

  • Enforce SRP, readability, and maintainability across classes and methods.
  • Provide clear rules for naming, error handling, and minimal coupling.
  • Use during development, refactoring, and PR reviews to align on style and structure.

Quick Start

Apply these rules when writing or reviewing code to ensure consistency across the project.

Frequently Asked Questions about clean-code-principles

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

FAQPage Schema
How do I enforce clean code standards during code reviews and PR discussions?

Apply clean code principles during PR reviews by checking rules for naming, SRP, error handling, and guard clauses to align on style and structure. This enforces readability and maintainability across the codebase.

What are guard clauses and how do they improve code readability?

Guard clauses enforce preconditions by handling edge cases early with immediate returns, flattening nested logic. This improves code readability and maintainability by reducing cognitive complexity.

How do I apply the Single Responsibility Principle when refactoring classes and methods?

Apply SRP during refactoring by ensuring each class and method manages exactly one responsibility. This minimizes coupling, aligns with clean code standards, and improves overall maintainability and reliability.

Can I use these clean code principles for new development or are they only for refactoring?

These clean code principles apply to both new development and refactoring. They define rules for naming, English logs, and line length to ensure consistent style and structure across the entire codebase lifecycle.

What is the best way to standardize naming conventions and error handling across a codebase?

The best way to standardize naming and error handling is to enforce clean code rules across all classes and methods. This provides clear guidelines to minimize coupling and align development practices.