clean

Review code for clean naming conventions — descriptive, intention-revealing names. Use when the user invokes /clean or asks for a clean code naming review.

跳到安装

clean：检查代码命名是否表达意图

检查变量、布尔值、函数和类型的名字是否清楚、是否符合项目惯例。重点看名称能否说明用途，布尔值是否像 isActive 一样表达判断，函数名是否描述实际行为。

操作说明

调用 /clean，或请求一次代码命名审查。检查范围包括不必要的缩写、小循环之外的单字母名称，以及命名风格是否一致。

引用来源

仓库: devinat1/engineering-skills
最近来源活动: 2026年9月4日 23:59
检测到的 SKILL.md 语言: 英语
星标: 0
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/devinat1/engineering-skills --skill clean

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

name: clean
description: Review code for clean naming conventions — descriptive, intention-revealing names. Use when the user invokes /clean or asks for a clean code naming review.
disable-model-invocation: true

# Clean Naming - Use descriptive, intention-revealing names. A variable name should tell you why it exists, what it does, and how it's used. - Avoid abbreviations and single-letter names outside of tiny loop scopes. - Use consistent naming conventions across the codebase (e.g., `camelCase` for variables, `PascalCase` for types/classes). - Name booleans as predicates: `isActive`, `hasPermission`, `shouldRetry`. - Name functions after what they do, not how they do it.

在 GitHub 查看

返回搜索返回安装

firecrawl

Scrape URLs, render JavaScript, crawl or map sites, search the web, and extract structured JSON through the private self-hosted Firecrawl API. Use for public or homelab web content without paid Firecrawl calls.

2026-09-09

leetcode-readiness

Use when the user invokes /leetcode-readiness or wants an evidence-based LeetCode progress assessment, interview-readiness date, or next-week problem plan from LeetCode and Obsidian history.

2026-09-05

break-it

Use to learn a system-design or performance concept by watching the naive version break under load and the pattern hold — "break it", "load test this", "where does this fall over", "/break-it <concept>". Builds a disposable Go+k6 lab; the user predicts the breaking point, runs it, sees the wall, applies the fix, re-runs. Load-measurable concepts only (pool exhaustion, missing cache, N+1, no rate limiting, no backpressure, no circuit breaker). NOT for refactoring or terminology — those are untangle / name-it.

2026-09-05

查看这个仓库的全部 Skills

clean

clean：检查代码命名是否表达意图

操作说明

来源信息

安装方式

检查来源文件

同仓库更多 Skills

clean：检查代码命名是否表达意图

操作说明

相关分享

同仓库更多 Skills