clean-code

Codify pragmatic coding standards for clean, maintainable software.

115|6|Updated Dec 28, 2025

Search Tags:#refactoring #readability #maintainability #best-practices #coding-standards #clean-code

Ready to run

npx skills add https://github.com/jewbetcha/opentrace --skill clean-code-jewbetcha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/jewbetcha/opentrace/tree/main/.agents/skills/clean-code
Command: npx skills add https://github.com/jewbetcha/opentrace --skill clean-code-jewbetcha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies pragmatic coding standards to keep projects lean, readable, and maintainable, avoiding over-engineering and excessive comments.

Core Features & Use Cases

Defines essential principles (SRP, DRY, KISS, YAGNI, Boy Scout) to reduce complexity and bugs.
Enforces naming rules, small focused functions, minimal arguments, and explicit control flow.
Provides guidelines for code structure, readability, and maintainability across teams.

Quick Start

Audit a sample module and refactor it to satisfy SRP, DRY, and KISS; rename ambiguous identifiers; replace deep nesting with guard clauses; ensure the code is concise and self-documenting.

Frequently Asked Questions about clean-code

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

FAQPage Schema

What are the best practices for writing clean and maintainable code?▼

Clean code standards enforce small focused functions, minimal arguments, and explicit control flow. This reduces complexity and bugs while ensuring software remains readable, testable, and extensible across teams without over-engineering.

How do I refactor a module to reduce complexity and improve readability?▼

Refactor modules by enforcing naming rules, small focused functions, and minimal arguments. Replace deep nesting with guard clauses to ensure the code is concise, readable, and self-documenting.

How do coding standards help reduce bugs in frontend and backend projects?▼

Coding standards reduce bugs by enforcing the Single Responsibility Principle and explicit control flow. This minimizes complexity and ensures frontend and backend projects remain maintainable and testable.

When should I avoid adding comments to my code?▼

Avoid excessive comments when your code is concise and self-documenting. Clean coding standards prioritize clear naming and explicit control flow over unnecessary comments to reduce complexity and maintain readability.

Does clean coding require specific frameworks or dependencies?▼

No, clean coding requires no specific frameworks or dependencies. It codifies pragmatic coding standards and structural guidelines that apply directly to any frontend or backend software development workflow.

What is the Boy Scout rule in clean code principles?▼

The Boy Scout rule dictates leaving code cleaner than you found it. It works alongside SRP, DRY, KISS, and YAGNI to progressively reduce complexity and improve maintainability across software development teams.