clean-code

Apply clean code principles to writing, reviewing, and refactoring code.

6|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill clean-code-repairyourtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill clean-code-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of writing code that is difficult to understand, maintain, and refactor, leading to increased development time and potential bugs.

Core Features & Use Cases

  • Improved Readability: Enforces clear naming conventions and function boundaries.
  • Reduced Complexity: Guides developers to write smaller, more focused functions.
  • Enhanced Maintainability: Promotes principles that make code easier to update and debug.
  • Use Case: When reviewing a pull request, use this Skill to identify and suggest improvements for code that is overly complex, poorly named, or contains redundant logic.

Quick Start

Apply clean code principles to the provided code snippet.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I improve code readability and maintainability when refactoring?

To improve code readability and maintainability, apply clean code principles like enforcing clear naming conventions, reducing function complexity, and writing smaller, focused functions to make code easier to debug.

What is the difference between clever code and clear code in software engineering?

The difference between clever code and clear code is maintainability. Clear code prioritizes readability and understandability by future developers over overly complex, condensed logic that creates debugging challenges.

How do I review a pull request for poor naming and redundant logic?

Review a pull request for poor naming and redundant logic by applying clean code principles to identify overly complex functions, suggest boundary improvements, and flag unclear naming conventions for refactoring.

Does this approach to clean code work for any programming language?

Yes, this clean code approach works for any programming language because it focuses on universal principles like class design, error handling, and function boundaries rather than language-specific syntax.

When should I not use clean code principles during development?

You should not strictly apply clean code principles when prototyping under extreme time constraints, as the initial focus may be on validating logic rather than ensuring immediate readability or maintainability.