Cmd Clean Code
Improve code readability without altering functionality using idiomatic best practices
Install
/plugin marketplace add Olshansk/agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Olshansk/agent-skills --skill cmd-clean-codegit clone --depth 1 https://github.com/Olshansk/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/.agents/skills/cmd-clean-code ~/.claude/skills/cmd-clean-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Clean Code Use these rules to improve code readability without altering functionality unless explicitly requested. ## Core Principles - Minimize cognitive load for human readers and agents. - Apply idiomatic best practices where they fit. - Preserve all business logic unless told otherwise. - Clarify comments and structure with bullet points where possible. ## Accepted Inputs - Full source files (`.proto`, `.go`, `.py`, `.md`, etc.). - Partial comments: package headers, method docs, inline notes. - Whole or partial functions. - Arbitrary code snippets (or any mix of the above). ## Response Requirements - Return the cleaned code wrapped in triple back-ticks. - Keep all identifiers (fields, params, classes, methods, etc.). - Add strategic whitespace for readability. - Convert paragraph-style comments into bullet points when feasible. - Do **not** delete or change original content unless asked. - Favor bullet lists whenever information is list-like. ## Team-Specific Edge Cases - Leave `TODO_???(???)` tags untouched. - Preserve callouts like `IMPORTANT`, `DEV_NOTE`, etc. - Maintain references to GitHub issues/PRs (e.g. "As of #XX ..."). - Keep every link and external reference. - Retain markers such as `CRITICAL`, `NB`, `DEV_NOTE`, `NOTE`; just clean up the following text. ### Handling Long Snippets - For grouped code (~5 lines) followed by a blank line, add a brief comment atop the block. - Keep existing comment hierarchy; just enhance readability. ## Nits & Edits
Details
- Skill name
cmd-clean-code- Repository
- Olshansk/agent-skills
- Path
.agents/skills/cmd-clean-code/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Cmd Clean Code skill do?
Improve code readability without altering functionality using idiomatic best practices
How do I install the Cmd Clean Code skill?
Claude Code plugin: /plugin marketplace add Olshansk/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cmd Clean Code popular?
It lives in Olshansk/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Cmd Agent Persona Set
9Olshansk/agent-skills
Prime the agent with a behavioral persona for the conversation
Cmd Code What
9Olshansk/agent-skills
Catch the user up on what the agent has been doing in the current session with 3-5 ultra-tight bullet points. Use when the user invokes /cmd-what, asks "what are you doing", "what did you do", "catch me up", "status", "where are we", or otherwise needs a fast situational summary of in-flight agent work.
Cmd Codex Review Plan
9Olshansk/agent-skills
Get a second opinion on the current plan from Codex (codex exec headless mode) before leaving plan mode. Pipes the plan to codex, captures critique and gap analysis, then proposes a revised plan with an explicit changelog of what changed and what was rejected. Triggers on "/cmd-codex-review-plan", "review plan with codex", "ask codex about this plan", or before approving auto mode on an exit-plan prompt.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Wp Local Env
9morrealev/wordpress-manager
Use when the user wants to work with a local WordPress development environment — WordPress Studio, LocalWP, or wp-env. Handles environment detection, site lifecycle, WP-CLI proxy, REST API access, symlink workflows, database operations, and preview/share.
Cmd Codex Review Unstaged
9Olshansk/agent-skills
Get a second opinion on what Claude just implemented from Codex (codex exec headless mode). Pipes Claude's summary plus the working-tree diff to codex, asks codex to leverage cmd-pr-follow-up and cmd-pr-edgecase methodology to surface bugs, test gaps, edge cases, and simplification opportunities, then synthesizes a prioritized iteration plan from the feedback. Triggers on "/cmd-codex-review-unstaged", "review my changes with codex", "have codex review what I just did", or after a non-trivial implementation pass before commit.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.