clean-code
实用的编码规范与重构建议，提升团队代码质量。
以简洁命名、小函数和良好错误处理提升代码可读性与可维护性。
把代码写成别人一看就懂、好改又可靠的样子：讲究命名、短小函数、单一职责和稳健的错误处理。适合在代码审查、重构或面对臃肿函数与臭味时使用。还会强调测试、注释与格式规范，目标是让代码对读者友好，降低后续维护成本。
▸ 展开 SKILL.md 英文原文
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
帮我安装这个 skill：https://raw.githubusercontent.com/wondelai/skills/main/clean-code/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/wondelai/skills/main/clean-code/SKILL.md"# Clean Code Framework A disciplined approach to writing code that communicates intent, minimizes surprises, and welcomes change. Apply these principles when writing new code, reviewing pull requests, refactoring legacy systems, or advising on code quality. ## Core Principle **Code is read far more often than it is written — optimize for the reader.** The read-to-write ratio is well over 10:1, so every naming choice, function boundary, and formatting decision either adds clarity or adds cost. Clean code reads like well-written prose: names reveal intent, functions tell a story one step at a time, and the Boy Scout Rule applies — always leave the code cleaner than you found it. ## Scoring