Why use this skill instead of a standard linter?

While linters check syntax and basic style, this skill provides higher-level architectural guidance and contextual decision-making for better code design and long-term readability.

Can this skill help with refactoring tasks?

Absolutely. It identifies unused imports, removes dead code, and ensures call sites are updated atomically while deleting redundant historical comments.

How does this skill handle file sizes?

It flags files exceeding 500 lines for immediate refactoring and suggests extraction when adding code to files already larger than 300 lines.

What is the main goal of the Code Hygiene skill?

It ensures code is clean, maintainable, and self-documenting by enforcing strict naming, commenting, and architectural standards during the coding process.

Does this skill support commenting best practices?

Yes, it prioritizes comments that explain design rationale (Why) and security markers over comments that simply describe what the code is doing (What).

Code Hygiene Standards

Name: Code Hygiene Standards
Author: EvanLavender13

byEvanLavender13

Developer Tools

Enforces clean code principles, descriptive naming conventions, and maintainable architectural patterns during development and refactoring.

About

The Code Hygiene skill acts as a proactive architectural guardrail for Claude, ensuring that code remains clean, readable, and easy to maintain. It mandates self-documenting code through precise naming, restricts file sizes to prevent bloated modules, and enforces a 'Why, not What' commenting philosophy. By integrating these standards into the development workflow, the skill helps developers avoid common pitfalls like archaeological comments, commented-out code, and violated single-responsibility principles, ultimately reducing technical debt and improving long-term project health.

Key Features

Automates the removal of archaeological comments and dead code
Checks for Single Responsibility Principle (SRP) compliance before adding new logic
Validates descriptive naming patterns for variables, booleans, and constants
0 GitHub stars
Enforces 'Why over What' commenting standards for better design rationale
Monitors file size limits to trigger necessary refactoring for large modules

Use Cases

Refactoring large, monolithic files into modular, well-organized components
Reviewing existing legacy codebases to identify and fix technical debt
Maintaining consistent coding standards across a team during active feature development

About

Key Features

Automates the removal of archaeological comments and dead code
Checks for Single Responsibility Principle (SRP) compliance before adding new logic
Validates descriptive naming patterns for variables, booleans, and constants
0 GitHub stars
Enforces 'Why over What' commenting standards for better design rationale
Monitors file size limits to trigger necessary refactoring for large modules

Use Cases

Refactoring large, monolithic files into modular, well-organized components
Reviewing existing legacy codebases to identify and fix technical debt
Maintaining consistent coding standards across a team during active feature development