clean-code

Name: clean-code
Availability: InStock
Author: PhaniJ

Enforce pragmatic coding standards for naming, function size, and structure.

1|Updated Jan 14, 2026

Search Tags:#refactoring #coding #code-quality #best-practices #code-review #naming #style-guide

Ready to run

npx skills add https://github.com/phanijapps/zbot --skill clean-code-phanijapps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/phanijapps/zbot/tree/main/gateway/templates/skills/clean-code
Command: npx skills add https://github.com/phanijapps/zbot --skill clean-code-phanijapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards ensure maintainable, readable, and efficient code by avoiding over-engineering and unnecessary comments.

Core Features & Use Cases

SRP, DRY, KISS, YAGNI, and Boy Scout principles for ensuring code clarity.
Naming and function rules to improve readability and maintainability.
Structured guidelines for code structure, guard clauses, and avoiding deep nesting.
Self-check procedures before completing edits to prevent regressions.

Quick Start

Apply these standards to every code change you make and perform the self-check before completing a task.

Frequently Asked Questions about clean-code

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

FAQPage Schema

What coding standards help improve code readability and maintainability during refactoring?▼

Pragmatic coding standards like SRP, DRY, KISS, YAGNI, and Boy Scout principles improve code readability and maintainability by enforcing clear naming, small functions, guard clauses, and minimal nesting during refactoring.

How do I apply guard clauses and naming rules to avoid deep nesting in my codebase?▼

Apply guard clauses and naming rules by enforcing structured guidelines that flatten conditional logic, use descriptive identifiers, and limit function size, which collectively avoid deep nesting and improve codebase clarity.

What is the best way to perform a self-check for code regressions before completing a task?▼

The best way to perform a self-check for regressions is to apply structured coding standards to every code change, verifying naming, function size, and structure rules before completing a task to prevent over-engineering.

Does this approach to code quality require avoiding comments and over-engineering?▼

Yes, this approach to code quality requires avoiding unnecessary comments and over-engineering by applying YAGNI and KISS principles, ensuring the codebase remains efficient, readable, and highly maintainable.

Can these coding standards be used for onboarding developers and conducting code reviews?▼

Yes, these coding standards can be used for onboarding developers and conducting code reviews, providing structured guidelines for function size and structure that guide developer behavior and ensure consistent quality.