skills.rest
JoaoPedroAmaral
JoaoPedroAmaralCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clean-code

Enforce clean-code standards on source code with verification scripts.

Updated Aug 27, 2026
Search Tags:#testing#refactoring#verification#code-review#naming#style-guide#clean-code
One-click install
npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill clean-code-joaopedroamaral
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/JoaoPedroAmaral/backBarbearia/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill clean-code-joaopedroamaral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides pragmatic coding standards and actionable rules to prevent over-engineering, unclear names, large functions, and unnecessary comments so that code is easier to read, maintain, and safely modify.

Core Features & Use Cases

  • Practical Rules: Enforces single responsibility, small functions, one level of abstraction, limited arguments, guard clauses, and meaningful naming.
  • Operational Guardrails: Requires thinking through imports, dependencies, tests, and co-editing dependent files before making changes.
  • Verification Workflow: Safer change process with mandatory self-checks and running designated verification scripts; maps agents to allowed scripts to avoid cross-role mistakes.
  • Use Case: Refactor a tangled UserService to split responsibilities, rename confusing identifiers, and run lint/test verification before marking the task complete.

Quick Start

Apply the clean-code rules to refactor UserService.ts to reduce complexity, rename unclear identifiers, and run any available verification scripts to confirm no regressions.

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 tangled function to follow clean code standards?▼

To refactor for clean code, enforce single-responsibility, split large functions into smaller units, apply guard clauses, rename unclear identifiers, and run verification scripts to confirm no regressions before completion.

What are the best practices for naming variables and structuring functions in maintainable code?▼

Maintainable code requires meaningful names, single-responsibility functions, one level of abstraction per function, limited arguments, and no unnecessary comments to ensure readability and safe modification across repositories.

Does this clean code approach work for both frontend and backend repositories?▼

Yes, these pragmatic clean-code standards apply to refactoring, bug fixes, and feature development across both frontend and backend repositories where naming, function structure, and small testable units are required.

How do I prevent over-engineering when writing production-ready code?▼

Prevent over-engineering by applying pragmatic coding standards that enforce small, testable units, guard clauses, and operational guardrails like thinking through imports and dependencies before making changes.

What verification steps should I run before marking a code refactoring task complete?▼

Before completing a refactoring task, run designated verification scripts, execute mandatory self-checks, and ensure co-edited dependent files are validated to avoid cross-role mistakes and confirm no regressions.

Related Skills

Explore More Software Engineering Skills→
vanducngvanducng
5

simplify

Simplify nested conditionals and long functions without changing behavior.

Community
Intermediate
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
thec3ukthec3uk

Global Coding Style

Enforce global coding style standards across files and languages.

Official
Basic
marcioaltoemarcioaltoe
14

code-standards

Enforce SOLID principles and Clean Code patterns across classes and modules.

Community
Advanced