skills.rest
fsolla
fsollaCOMMUNITY
Explore all skills by this author →
Website𝕏@franciscosollaGitHub

clean-code

Analyze code for smells and suggest specific refactoring steps.

Updated Jul 31, 2026
Search Tags:#code review#refactoring#unit testing#clean code#technical debt#software craftsmanship
One-click install
npx skills add https://github.com/fsolla/teqo --skill clean-code-fsolla
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/clean-code
Command: npx skills add https://github.com/fsolla/teqo --skill clean-code-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the accumulation of technical debt, unreadable functions, and inconsistent naming conventions that slow down development and increase the risk of bugs.

Core Features & Use Cases

  • Code Quality Scoring: Evaluates code on a 1-10 scale based on readability, function size, and test coverage.
  • Refactoring Guidance: Provides actionable steps to apply principles like Single Responsibility, Command-Query Separation, and the Boy Scout Rule.
  • Use Case: When reviewing a pull request with a 500-line function, use this Skill to identify specific extraction opportunities and naming improvements to make the logic modular and testable.

Quick Start

Analyze the provided function for code smells and suggest specific refactoring steps to improve its readability and maintainability.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I identify code smells in a large legacy function for refactoring?▼

Code review for refactoring targets unreadable functions by applying clean code principles like the Single Responsibility Principle. This eliminates technical debt by evaluating function size and providing actionable steps to extract modular, testable logic.

What is the best way to establish consistent coding standards across a codebase?▼

Establishing consistent coding standards across a codebase requires applying clean code principles such as meaningful naming and robust error handling. This eliminates inconsistent naming conventions and reduces the accumulation of technical debt.

How does code quality scoring evaluate readability and maintainability?▼

Code quality scoring evaluates maintainability by rating code on a 1-10 scale based on readability, function size, and test coverage. This mechanism highlights technical debt and identifies specific areas for targeted refactoring.

Can I apply the Boy Scout Rule and Command-Query Separation during a code review?▼

You can apply the Boy Scout Rule and Command-Query Separation during code review to get actionable refactoring steps. These clean code principles improve software maintainability by ensuring functions perform single responsibilities.

When do I need targeted refactoring patterns to eliminate technical debt?▼

You need targeted refactoring patterns to eliminate technical debt when accumulation slows development and increases bug risks. Applying clean code principles like meaningful naming and robust error handling resolves these maintainability issues.

Related Skills

Explore More Software Engineering Skills→
tswrtswr
1

refactoring

Restructure C++, Java, Python, and Rust code without altering external behavior.

Community
Advanced
0xjc65eth0xjc65eth
4

test-runner

Detect test frameworks and generate, run, and report automated tests.

Community
Advanced
darsoohoodarsoohoo

coding-rules

Enforce coding standards like 0-2 parameters and explicit error handling.

Community
Advanced
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced