clean-code
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "clean-code" from https://skillstore.io/skills/sickn33-clean-code.md and its manifest at https://skillstore.io/api/skills/sickn33-clean-code/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "clean-code". Review a pull request with large functions and unclear names.
Expected outcome:
- Highlights vague names that hide business intent.
- Flags functions with mixed abstraction levels and too many responsibilities.
- Suggests smaller reviewable changes with clearer tests.
Using "clean-code". Refactor a legacy service before adding features.
Expected outcome:
- Identifies side effects, long methods, and data structure leakage.
- Ranks refactoring steps by clarity, risk, and maintenance value.
- Recommends tests that protect behavior during cleanup.
Using "clean-code". Create a shared Clean Code checklist for a team.
Expected outcome:
- Groups review criteria by naming, functions, comments, errors, tests, and classes.
- Keeps each checklist item actionable and easy to apply during review.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (12)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-clean-code/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-clean-code?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-clean-code?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-clean-code/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-clean-code.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). clean-code security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-clean-code/audits/5BibTeX citation
@techreport{sickn33-sickn33-clean-code-2026,
author = {sickn33},
title = {clean-code security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-clean-code/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "clean-code security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-clean-code/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-clean-code:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-clean-code
2026-08-21
doubleslashse-clean-code
2026-08-21
benny9193-clean-code
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Review the selected code for intention-revealing names. Suggest clearer names for variables, functions, classes, and methods.
Evaluate each function for size, one clear purpose, abstraction level, side effects, and argument count. Prioritize the most useful fixes.
Analyze this module with Clean Code principles. Identify code smells, rank refactoring steps, and explain the expected maintenance benefit.
Create a Clean Code review checklist for this repository. Cover naming, functions, comments, errors, tests, objects, and classes.
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.
Avoid
- 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.