code-polish
Skill0 starsChanged 5 months agoMITView on GitHub
Polish code formatting/style and trim redundancy WITHOUT changing behavior. Use to tidy layout, enforce consistent style (indentation, quotes, import order, naming), run the project's formatter + linter --fix, remove dead code / unused imports / commented-out blocks, and replace verbose constructs with shorter equivalent ones (guard clauses, early return, destructuring, optional chaining). Complements code-simplification (which lowers cognitive/logical complexity); this one focuses on format, consistency, and compactness. Use when asked to format, tidy, polish, clean up, or 精简 code. Triggers: format code, tidy, polish, clean up code, optimize formatting, trim, 优化代码格式, 精简代码, 整理代码, 代码格式化.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- PaulRBerg/dot-agentstheir own version, first seen Nov 6, 2026
- PaulRBerg/agent-skillstheir own version, first seen Oct 24, 2026
- AlexMini2517/skillstheir own version, first seen Sep 9, 2026
- sohamM97/claude-skillstheir own version, first seen Aug 21, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- PaulRBerg/agent-skills★ 104same name
- PaulRBerg/dot-agents★ 6same name
- AlexMini2517/skills★ 1same name
- sohamM97/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Files
Code Polish — 代码格式优化与精简
在不改变行为的前提下，统一格式、去除冗余、让代码更紧凑可读——与降逻辑复杂度的
code-simplification互补。
在不改变行为的前提下，让代码更整洁、风格统一、紧凑可读。与 code-simplification(降逻辑复杂度) 互补——这个偏格式 / 风格 / 冗余 / 紧凑度。
铁律（先记住）
- 不改行为 —— 改前确认有测试或能验证；改完跑测试/类型检查，绿了才算数。
- 工具优先 —— 能交给 formatter/linter 的绝不手改。
- 小步可回滚 —— 一类问题改一批、跑测、提交；大批量用 codemod/脚本，别手工。
- 只动格式与冗余 —— 同一次改动不夹带功能/逻辑变更，保持 diff 干净。
- 贴项目规范，不按个人偏好 —— 先看
.editorconfig/.prettierrc/CLAUDE.md/ 邻近代码。
流程（按序）
- 定范围 —— 哪些文件/目录；确认有测试兜底或可手工验证。
- 格式层（自动） —— 跑项目的 formatter（prettier / black / gofmt / clang-format / rustfmt…）+
lint --fix：统一缩进、引号、分号、空行、import 排序与去未用、行宽。 - 精简层（人工，按信号） —— 见下表，逐条等价替换。
- 验证 —— 跑测试 + 类型检查 + lint；确认行为不变。
- 自检 —— 这版真更好读吗？diff 是否只含格式/精简、无意外逻辑改动？
- 原子提交 —— 单独一个
refactor/style:提交，信息写清"仅格式与精简、行为不变"。
精简信号 → 等价更简洁写法
| 信号 | 改法 |
| 死代码 / 未用 import / 注释掉的代码 | 删（孤立项先列出确认再删） |
| 深层 if/else 包裹主体 | 护卫子句 + 早返回（early return） |
| 多余中间变量 / 一次性变量 | 内联 |
x ? x : y、x != null ? x.a : undefined | 空值合并 ?? / 可选链 ?. |
| 重复对象取字段 | 解构 |
| 多次重复的逻辑（≥3 次） | 抽成函数/常量 |
| 冗长布尔判断 | 提取具名布尔（isAdmin 胜过裸表达式） |
| 手写循环做 map/filter/reduce | 用数组方法（前提：不牺牲可读性） |
反模式（别做）
- 为了缩行数牺牲可读性（明确 > 聪明，一行嵌套三元不如几行清楚）。
- 在格式提交里偷偷改行为 / 改公共接口。
- 全仓库一把梭手工重排（用工具 + 分批）。
- 跨项目套个人风格、无视既有约定。
检验（过不了就回滚）
行为不变（测试绿）？符合项目格式规范？diff 干净只含格式/精简？队友会一眼批准？
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.