skills.rest
BrunoSantanaDeveloper
BrunoSantanaDeveloperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clean-code

Enforce concise, readable coding practices across software engineering tasks.

Updated Jan 27, 2026
Search Tags:#refactoring#maintainability#coding-standards#clean-code#srp#kiss#dry
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill clean-code-brunosantanadeveloper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/clean-code
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill clean-code-brunosantanadeveloper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards help teams write concise, readable, and maintainable code while avoiding over-engineering and unnecessary comments.

Core Features & Use Cases

  • Enforces SRP, DRY, KISS, YAGNI principles to keep code simple and focused
  • Encourages meaningful naming, small functions, and minimal side effects
  • Use Case: refactor a large function into smaller, testable units without changing behavior

Quick Start

Apply the clean-code guidelines to the next function you write, keeping it small, expressive, and free of unnecessary comments.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I refactor a large function into smaller, testable units without changing behavior?▼

Refactoring large functions involves applying SRP to split responsibilities into smaller, focused units, enforcing DRY to eliminate duplication, and ensuring minimal side effects throughout the process.

What are the best coding standards to keep code concise and maintainable?▼

Maintainable code relies on KISS and YAGNI principles to avoid over-engineering, encourages meaningful naming for readability, and enforces small functions with minimal side effects.

When should I apply clean code principles during software engineering tasks?▼

Apply clean code principles when writing new functions, refactoring modules, reviewing pull requests, and enforcing naming conventions across projects to reduce complexity and improve readability.

Does enforcing DRY and SRP help reduce code complexity in existing modules?▼

Enforcing DRY and SRP reduces code complexity by eliminating redundant logic and isolating responsibilities, making modules easier to read, test, and maintain across the project.

Why does over-engineering make code harder to maintain?▼

Over-engineering introduces unnecessary abstractions and comments that obscure intent, while violating YAGNI and KISS principles ultimately increases the maintenance burden and reduces readability.

Can I use these refactoring guidelines for pull request reviews?▼

These guidelines apply directly to pull request reviews by enforcing concise coding practices, meaningful naming, small functions, and minimal side effects to ensure maintainable code.

Related Skills

Explore More Software Engineering Skills→
xkazm04xkazm04

Architect

Analyze codebases for architectural weaknesses and anti-patterns.

Community
Advanced
ydnikolaevydnikolaev
8

qa-lead

Plan and validate E2E, API, and UI tests with generated reports.

Community
Advanced
grasberggrasberg
3

clean-code

Enforces SRP, DRY, KISS coding standards across AI projects via linting and refactoring.

Community
Intermediate
united-software-platformunited-software-platform
1

architect-reviewer

Analyze and validate high-level system designs and architectural patterns.

Official
Advanced