Skip to content
Skills Library
Programming · Building & coding

code-polish

/code-polish

Polish changed code when the user explicitly asks, or when an active workflow requests post-implementation simplification and risk-profiled review over a fixed file scope.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Polish changed code when the user explicitly asks, or when an active workflow requests post-implementation simplification and risk-profiled review over a fixed file scope.

Arguments

/code-polish [paths] [--simplify] [--review] [--with-profile <name>] [--skip-profile <name>]
Original author description

Polish changed code when the user explicitly asks, or when an active workflow requests post-implementation simplification and risk-profiled review over a fixed file scope.

How it works

  1. Modes
  2. Fixed Scope
  3. Simplify
  4. Review and Fix
  5. Verification and Report
Original SKILL.md headings · 100 lines, 794 words
SKILL.md preview
---
argument-hint: "[paths] [--simplify] [--review] [--with-profile <name>] [--skip-profile <name>]"
name: code-polish
description:
  "Polish changed code when the user explicitly asks, or when an active workflow requests post-implementation
  simplification and risk-profiled review over a fixed file scope."
---

# Code Polish

Resolve scope once. Make only high-confidence simplifications. Fix defects supported by evidence according to their
risk. Verify the final state.

## Modes

- `--simplify`: simplify only.
- `--review`: review and fix only.
- Neither or both: simplify, then review the simplified result.
- `--with-profile <name>` / `--skip-profile <name>`: add or suppress review profiles. Skip wins.

## Fixed Scope

1. Require a Git repository.
2. Use explicit paths, patterns, ranges, natural-language targets, or a supplied `resolved-scope` block when present.
   Otherwise, use only files modified in this session. If session history is unavailable, use all uncommitted tracked
   and untracked files.
3. Exclude lockfiles, generated outputs, vendored code, minified bundles, and large data snapshots from manual review
   unless explicitly requested. Validate relevant excluded outputs through their generator, schema, or invariants.
4. Resolve and retain one authoritative scope set and optional exclusions for execution. Do not broaden or recompute
   scope later. Stop if it is empty.

## Simplify

Preserve public contracts, inputs, outputs, side effects, error behavior, performance-sensitive characteristics,
telemetry, and operational guards. Apply only changes with a concrete comprehension or defect-risk benefit:

- flatten avoidable control-flow nesting.
- clarify misleading names or dense transforms.
- remove real duplication when the abstraction reduces total complexity.
- tighten local types and contracts without broad churn.
- remove only dead code caused by this session's edits.

Do not split by line count, perform architecture cleanup, convert sync/async APIs, add speculative configurability, or
replace readable duplication with a one-use abstraction. A no-op is a valid result.

## Review and Fix

Judge the diff against the user's request. Prioritize `CRITICAL → HIGH → MEDIUM → LOW`:

- **CRITICAL**: exploitable security, data loss, or critical outage path.
- **HIGH**: behavior, error-path, boundary, or performance defect affecting core behavior.
- **MEDIUM**: resource leak, complexity hotspot, test gap, over-scoped change, speculative complexity, or weak success
  criterion likely to cause defects.
- **LOW**: localized clarity or style issue with a real maintenance cost.

Every finding must cite a verified location, triggering input/state, failure mode, blast radius, and evidence in the
changed code. Merge duplicates and apply the smallest defensible fix. Resolve ambiguous intent from the request and
repository first. State routine assumptions. Ask only when the answer changes behavior or scope. While that item waits,
continue independent in-scope fixes.

Select every applicable profile and read it once. Read all selected profiles together in one parallel turn:

| Surface                                                       | Profile                 |
| ------------------------------------------------------------- | ----------------------- |
| auth, secrets, crypto, external input/network, unsafe parsing | `security`              |
| env, config, timeouts, retries, pools, limits                 | `configuration`         |
| Go behavior, concurrency, context, errors                     | `go`                    |
| Rust, Cargo/workspaces, async/concurrency, unsafe/FFI         | `rust`                  |
| TypeScript types, modules, packages, async behavior           | `typescript`            |
| Python services, scripts, async, packaging, data IO           | `python`                |
| shell, CI, deploy, installers, quoting                        | `shell`                 |
| CSV/JSON/YAML/binary, schemas, migrations, generated data     | `data-formats`          |
| naming and intent clarity                                     | `naming` unless skipped |

Profiles live at `references/profiles/<name>.md`. Missing selected profiles are a stop condition.

## Verification and Report

Run the narrowest formatter/lint, targeted tests, typecheck, and invariant checks that prove the final touched behavior.
Broaden only for shared contracts. Name skipped checks and why.

Summarize scope with the file count and smallest useful repository-relative roots, globs, ranges, or user-supplied
targets. Do not enumerate every file merely to prove scope. Name individual paths only for a small explicit scope or to
clarify exceptions and findings.

Findings include severity, location, impact, evidence, fix, and confidence. A residual risk states the assumption,
consequence if wrong, and how to check it.

Under `Issues and caveats`, group verified fixes with evidence as `Resolved`, and remaining problems, limitations, or
unverified assumptions as `Open`, with their impact and next step. Omit empty groups. Report each item once. Put neutral
context and agreed decisions under changes or scope.

Reserve `blocker` for something preventing required work and `risk` for a specific potential adverse outcome. A
workaround leaves an item open when the underlying issue still affects the result. Completion requires fixed scope,
traceable edits/findings, and validation evidence.

Lead a successful report with `### ✨ Code polish — ✅ complete`, then summarize scope, meaningful changes, and
verification. For small results, use short prose. Add tables or sections only when they clarify multiple changes or
findings. Honor the user's requested format.

When review ran and found no defects, state `✅ No verified review findings.` If a stop condition below prevents
completion, lead with `### ✨ Code polish — ⛔ blocked` and report the evidence and required decision. Keep severity
tokens, profile IDs, commands, locations, reproduction inputs, and security evidence exact and undecorated.

Stop when behavior parity or required high-risk validation cannot be established, or a fix requires an unrequested
public-contract change or larger redesign.
Files in this package (11)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB
  • references/profiles/configuration.md 1 KB
  • references/profiles/data-formats.md 1 KB
  • references/profiles/go.md 2 KB
  • references/profiles/naming.md 1 KB
  • references/profiles/python.md 1 KB
  • references/profiles/rust.md 2 KB
  • references/profiles/security.md 1 KB
  • references/profiles/shell.md 1 KB
  • references/profiles/typescript.md 1 KB

Versions

RepositoryScoreLicence
This page · PaulRBerg/agent-skills90MIT
FrancoStino/opencode-skills-collection100MIT
sickn33/agentic-awesome-skills100MIT

Database snapshot: 13.11.2026 · package version b964d09113ff (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100polish
    Use only when the user explicitly asks for a combined quality pass over changed code, or when the active ship workflow invokes it — "polish the diff", "polish my changes", "clean up my changes", "run all the reviewers". Diff-scoped by default; accepts an optional path argument.
  • 100code-review
    Review changed code for quality, security, and architecture compliance. Use only when the user explicitly requests local review or a PR finding requires it.
  • 100code-simplify
    Use when code needs simplification — recently modified code by default, or a specified scope.
  • 100code-review
    Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.
  • 90cmk:delivery-simplify
    Use when the user asks to "simplify", "clean up the diff", "polish the changed code", or "run a simplify pass" without changing behavior — or when phase 3b of `cmk:delivery-pipeline` needs a whole-branch quality cleanup. Produces a behavior-preserving polish of the changed…
  • 100code-review
    Review pyDeprecate pull requests and changed code for correctness, compatibility, security, performance, tests, documentation, and CI. Use for code reviews and regression assessments, not implementation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.