polish

Harmonize naming, comments, imports, and presentation to match codebase conventions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/nokusukun/sublime --skill polish-nokusukun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/nokusukun/sublime/tree/main/polish
Command: npx skills add https://github.com/nokusukun/sublime --skill polish-nokusukun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero-behavior-change final pass. Harmonizes naming, comments, imports, and presentation with the codebase's existing conventions; removes banner comments, emoji, tutorial-voice narration, and JSDoc-that-mirrors-types. Use as the last step before shipping a change — after audit, harden, and any refactors. Never changes behavior; never rewrites; never redesigns.

Core Features & Use Cases

  • Naming consistency across files and modules; canonicalizing identifiers and drift
  • Comment and banner cleanup: remove line-narration, emoji, and tutorial voice; tidy docstrings
  • Import/file-top hygiene: sort imports, remove unused, normalize formatting; unify top-level structure
  • Signature and shape alignment: ensure parameter order, types, and export style match project conventions
  • Final-presentation polish: trailing whitespace, quotes, and formatting to ship-ready diffs

Quick Start

Run the polish pass on the current changes to harmonize naming, comments, and imports without altering behavior.

Frequently Asked Questions about polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up AI-generated code comments and narration before shipping?

Code comment cleanup removes tutorial-voice narration, banner comments, and emoji by harmonizing comments to match existing codebase conventions without altering behavior. It tidies docstrings and eliminates JSDoc that merely mirrors types.

What is the best way to fix naming drift across files in a repository?

Fixing naming drift involves canonicalizing identifiers across files and modules to match the project's existing style conventions. This final-pass harmonization ensures naming consistency without changing code behavior or semantics.

How do I sort imports and remove unused ones without changing code behavior?

Import hygiene sorts imports, removes unused ones, and normalizes formatting to unify the top-level file structure. It operates under a zero-behavior-change policy to ensure semantics remain completely preserved.

Does a final-pass code polish step change my application's logic or runtime behavior?

A final-pass code polish never changes application logic or runtime behavior. It strictly harmonizes presentation, naming, and formatting to match codebase conventions while preserving all original semantics.

When should I run a code style and formatting polish in my development workflow?

Run code polish as the last step before shipping a change, after completing audits, hardening, and refactors. It prepares ship-ready diffs by fixing trailing whitespace, quotes, and formatting.

Can I use code polish to rewrite or redesign my existing functions?

Code polish cannot rewrite or redesign existing functions. It strictly harmonizes signatures, export styles, and presentation to match project conventions, guaranteeing zero behavior change without altering the underlying design.