skills.rest
tayiorbeii
tayiorbeiiCOMMUNITY
Explore all skills by this author →
GitHub

clean-code

Enforces clean coding discipline across naming, functions, error handling, and unit testing with rubric-based scoring.

Updated Aug 23, 2026
Search Tags:#code review#refactoring#unit testing#error handling#code smells#naming conventions#single responsibility
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit --skill clean-code-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/tayiorbeii/paperclip-factory-kit/tree/main/skills/clean-code
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit --skill clean-code-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clean code eliminates the slowdowns and bugs caused by hard-to-read code, misleading names, oversized functions, inconsistent error handling, and brittle or missing tests.

Core Features & Use Cases

  • Meaningful Naming: Use intent-revealing names so the code communicates clearly without relying on comments.
  • Small, Focused Functions: Apply single-responsibility boundaries, minimal arguments, and clear control flow.
  • Disciplined Error Handling & Testing: Separate error concerns, avoid nulls, and use clean, readable tests to make refactoring safe.
  • Refactoring Against Smells: Diagnose common code smells (duplication, long functions, feature envy, magic numbers) and refactor incrementally with tests.

Quick Start

Use the clean-code skill to review a pull request for readability issues and produce a prioritized 0–10 score with specific refactoring actions.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I review a pull request for code smells and readability issues?▼

Refactor legacy code by diagnosing common code smells like duplication, long functions, and magic numbers, then applying incremental refactoring guided by clean, readable unit tests. This ensures safe structural improvements while maintaining single-responsibility boundaries.

What is the best way to enforce single responsibility and naming conventions in new code?▼

Enforce single responsibility and naming conventions by applying intent-revealing names and minimal argument boundaries to functions. This ensures code communicates clearly without relying on comments, directly improving readability and maintainability.

How does clean error handling improve unit testing and refactoring safety?▼

Clean error handling improves unit testing by separating error concerns and avoiding nulls, which makes tests clean and readable. This disciplined approach makes refactoring safe by ensuring code behavior remains predictable during structural changes.

Can I use a rubric-based assessment to score maintainability of legacy modules?▼

You can score legacy module maintainability using a rubric-based 0–10 assessment that evaluates code readability, function size, and test quality. This targets specific code smells and provides actionable refactoring guidance aligned with clean architecture practices.

Related Skills

Explore More Software Engineering Skills→
cosmicstack-labscosmicstack-labs
364

clean-code

Assess code quality against a Clean Code scoring rubric.

Official
Basic
tnkmr32tnkmr32

refactor

Guide safe, incremental refactoring of functions, classes, and modules with test verification.

Community
Basic
nesnilnehcnesnilnehc
7

review-architecture

Audit codebase architecture and report findings on modules, layers, and dependencies.

Community
Intermediate
CassiiopeiaCassiiopeia
7

pro-refactor-analyze

Detect code smells and generate refactoring plans without modifying source code.

Community
Advanced