skills.rest
hatlesswizard
hatlesswizardCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clean-code-ch17-smells-and-heuristics

Catalog all 66 code smells across a project using a canonical checklist.

4|Updated Mar 28, 2026
Search Tags:#refactoring#heuristics#static-analysis#software-quality#coding-standards#code-review#code-smells
One-click install
npx skills add https://github.com/hatlesswizard/clean-code-skills --skill clean-code-ch17-smells-and-heuristics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code-ch17-smells-and-heuristics
Source: https://github.com/hatlesswizard/clean-code-skills/tree/main/ch17-smells-and-heuristics
Command: npx skills add https://github.com/hatlesswizard/clean-code-skills --skill clean-code-ch17-smells-and-heuristics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catalogs, references, and a unified 66-item checklist of code smells to guide systematic code-quality improvements.

Core Features & Use Cases

  • Comprehensive master checklist covering C1-C5, E1-E2, F1-F4, G1-G36, J1-J3, N1-N7, T1-T9.
  • Aids code reviews, teaching, and technical debt audits by providing a canonical reference for smells and heuristics.
  • Supports structured refactoring and architecture reviews by enabling consistent terminology around smells.

Quick Start

Review the Master Checklist in SKILL.md to begin auditing a codebase for all 66 smells.

Frequently Asked Questions about clean-code-ch17-smells-and-heuristics

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

FAQPage Schema
What are code smells and how do heuristics help identify them?▼

Code smells are structural weaknesses indicating deeper design issues. Heuristics apply standardized rules to systematically catalog these 66 specific patterns across a codebase, guiding consistent reviews and technical debt audits.

How do I audit a codebase for code smells using a structured checklist?▼

To audit a codebase for code smells, review your source code against a canonical 66-item checklist covering C1 through T9 categories. This structured taxonomy enables systematic identification of refactoring targets and technical debt.

Can I use this code smell checklist for refactoring in any programming language?▼

Yes, this code smell checklist applies to codebases across multiple programming languages. It provides a centralized reference for identifying smells in both educational and production environments, supporting language-agnostic code reviews.

What is the best way to catalog technical debt during a code review?▼

The best way to catalog technical debt is applying a unified checklist of 66 code smells and heuristics. This provides consistent terminology and scoring guidance to reliably assess and document software quality issues during reviews.

How many code smells are covered in a comprehensive refactoring taxonomy?▼

A comprehensive refactoring taxonomy covers 66 specific code smells and heuristics. This master checklist spans categories C1-C5, E1-E2, F1-F4, G1-G36, J1-J3, N1-N7, and T1-T9 to enable reliable architecture and code-quality assessments.

Related Skills

Explore More Software Engineering Skills→
ResearAIResearAI
3.3k

baseline

Standardize a reference object for quest evaluation with plan and checklist requirements.

Community
Advanced
HsnSaboorHsnSaboor

refactoring-expert

Refactors code using Martin Fowler's catalog and functional programming practices.

Community
Advanced
CloakingGhostCloakingGhost

qa-agent

Automate code review, error fixing, and structural improvements via static analysis.

Community
Intermediate
ShubhamsabooShubhamsaboo
131.7k

python-expert

Review Python code for correctness, type safety, performance, and style.

Community
Basic