# Improve Code Quality With Clean Code Reviews

Messy code slows reviews, refactoring, and feature work. This skill guides Claude, Codex, and Claude Code through practical Clean Code checks.

## Install

```bash
npx skillstore add sickn33/clean-code
```

## Metadata

- Status: approved
- Slug: sickn33-clean-code
- Skillstore revision: r1
- Version status: missing
- Tree hash: 9c6e7ff8c524e671c54ce65d59547978071f4b3e6dfb19dc01116567b0dc69e4
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/clean-code
- Ref: 01171b582d636c013315c5e0d969c64f8d9cdff2
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-clean-code
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-clean-code/manifest

## Capabilities

- Applies naming guidance for variables, classes, and methods.
- Reviews functions for size, single purpose, abstraction level, and argument count.
- Assesses comments, formatting, object structure, error handling, tests, and class design.
- Identifies code smells such as rigidity, fragility, immobility, and needless repetition.
- Provides a checklist for clean code review and refactoring.

## Use Cases

- Review Pull Requests: Apply consistent Clean Code feedback before changes reach the main branch.
- Refactor Legacy Code: Find unclear names, large functions, hidden side effects, and design smells before modifying old modules.
- Set Team Standards: Turn Clean Code principles into shared review criteria for naming, comments, tests, and class design.

## Prompt Templates

### Review Naming

```
Review the selected code for intention-revealing names. Suggest clearer names for variables, functions, classes, and methods.
```

### Check Function Design

```
Evaluate each function for size, one clear purpose, abstraction level, side effects, and argument count. Prioritize the most useful fixes.
```

### Plan a Refactor

```
Analyze this module with Clean Code principles. Identify code smells, rank refactoring steps, and explain the expected maintenance benefit.
```

### Create Review Criteria

```
Create a Clean Code review checklist for this repository. Cover naming, functions, comments, errors, tests, objects, and classes.
```

## Limitations

- It provides guidance, not automated static analysis.
- It does not execute tests or inspect runtime behavior.
- It does not replace security review or performance profiling.
- It may differ from a team's local style guide.

## Best Practices

- Provide the relevant code and the team style guide together.
- Ask for prioritized findings when reviewing large modules.
- Pair refactoring advice with tests that protect existing behavior.

## Anti Patterns

- Do not ask for broad rewrites without a clear goal.
- Do not treat every Clean Code guideline as an absolute rule.
- Do not skip tests when changing behavior during refactoring.

## Security Audit

- Audited at: 2026-07-06T22:39:34.222\+00:00
- Summary: All static findings are false positives caused by Markdown inline code, fenced code examples, technical terms, or source attribution. I found no executable shell command, system reconnaissance instruction, unauthorized network behavior, or prompt injection attempt in SKILL.md.

## Stats

- Views: 152
- Downloads: 20
- Favorites: 0
- Popularity score: 0