clean-code

Apply Clean Code principles to improve naming, structure, and comments in codebases.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill clean-code-dgouron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/DGouron/review-flow --skill clean-code-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean Code guidance helps developers produce readable, durable, and consistent code by applying established principles. It addresses naming, small functions, meaningful comments, and avoidance of code smells, complementing neighboring skills such as /solid and /anti-overengineering. Activate during the REFACTOR phase of the TDD cycle and during implementation self-review.

Core Features & Use Cases

  • Readability-first guidelines for naming, function size, and comments.
  • Structured approach to refactoring that preserves behavior while improving intent.
  • Use Case: during a PR/MR review, ensure naming conventions and decomposition to reduce cognitive load.

Quick Start

Apply these guidelines during the next refactor to improve readability and reduce code smells.

Frequently Asked Questions about clean-code

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

FAQPage Schema
What is clean code and when should I apply refactoring principles?

Clean code is a set of principles to improve readability, maintainability, and consistency. Apply refactoring during the TDD refactor phase, self-reviews, and PR/MR reviews to reduce cognitive load and fix code smells.

How do I refactor code to improve readability and maintainability?

Refactor code to improve readability by enforcing naming conventions, reducing function size, adding meaningful comments, and following consistent project patterns. This structured approach preserves behavior while clarifying intent across modules.

What are common code smells and how do I fix them during a self-review?

Common code smells include poor naming, oversized functions, and inconsistent formatting. Fix them during a self-review by applying clean code principles to decompose functions, update naming conventions, and align with project patterns.

Can I use clean code guidelines for pull request and merge request reviews?

Yes, clean code guidelines are designed for PR and MR reviews. They ensure naming conventions and function decomposition are applied, reducing cognitive load and improving codebase consistency across modules.

Does applying clean code principles conflict with SOLID design rules?

Clean code principles complement SOLID design rules. Clean code focuses on readability, naming, and function sizing, while SOLID addresses structural design, working together during refactor phases to improve maintainability.

Why does my refactored code still have poor readability after reducing function size?

Poor readability persists after reducing function size if naming conventions, meaningful comments, and consistent formatting are neglected. Clean code requires aligning all these elements with established project patterns to truly improve intent.