菜单
Use when reviewing or writing refactors, renames, or migrations where old interfaces may linger as aliases, re-exports, wrappers, fallback branches, deprecated flags, or other compatibility cruft. Especially relevant when changed code keeps both old and new paths alive inside the same repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Tzeusy/ai-bootstrap --skill cruft-cleanup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | cruft-cleanup |
| description | Use when reviewing or writing refactors, renames, or migrations where old interfaces may linger as aliases, re-exports, wrappers, fallback branches, deprecated flags, or other compatibility cruft. Especially relevant when changed code keeps both old and new paths alive inside the same repo. |
| metadata | {"owner":"tze","authors":["tze","OpenAI Codex"],"status":"active","last_reviewed":"2026-06-12"} |
LLMs preserve old interfaces "just in case." In same-repo refactors, that leaves dead wrappers, aliases, and fallback paths instead of a finished migration.
When refactoring, migrating, or renaming, leave only the new code path unless backward compatibility is explicitly required.
If you changed it, finish the job. Every callsite, import, reference, and test uses the new interface. Delete the old one — not deprecate, not re-export, not alias.
Catch yourself writing a compatibility alias, wrapper, or fallback? Stop and update the callers instead.
| File | Read when | Content |
|---|---|---|
references/audit-flow.md | Every real use of this skill | Proactive and reactive workflow, grep strategy, and review sequence |
references/patterns-to-delete.md | You need concrete examples of cruft | Common shim/fallback/tombstone patterns to remove |
references/compat-boundary.md | You suspect compatibility might be legitimate | Hard boundary for when old interfaces may stay temporarily |
Use for project-level engineering governance in any repository — bootstrap or audit the knowledge architecture (doctrine, specs, topology, standards), concretize a feature request into a spec delta, amend a spec found wrong mid-implementation, reconcile specs against implementation, run a repo-wide health audit, decide what to work on next via spec-driven planning, milestone synthesis, and doctrine-grounded feature ideation, or run a recurring vision-pursuit audit that generates the next best moves toward the project's ideal. Route to exactly one subskill per task. Triggers: "project shape", "bootstrap docs", "what should we work on next", "should we build this", "I want to add X", "spec this feature", "the spec is wrong", "break this down", "review this project", "audit the codebase", "does the code match the spec", "what's the next milestone", "brainstorm features", "run the vision pursuit", "relentlessly improve this project".
Use when analyzing or bootstrapping the five-pillar knowledge architecture of a software project: about/heart-and-soul (doctrine), about/legends-and-lore (RFCs/design contracts), about/lay-and-land (topology), about/craft-and-care (execution-quality standards), and openspec/ (capability specs at root). Use when: starting a new project's knowledge structure, auditing documentation health, onboarding, deciding where knowledge belongs, or mapping system topology. Triggers: "project shape", "bootstrap docs", "where should this go", "what's this project about", "project pillars", "heart and soul", "spec structure", "knowledge architecture", "system map", "topology", "lay of the land", "set up project structure".
Use for engineering-quality work on any change or codebase — holding an implementation or review to the engineering quality bar, code readability, test-suite rigor, module boundaries and dependency chains, diagnosing hard bugs and flaky failures to root cause, post-refactor cruft cleanup, codebase documentation, creating or reviewing skills against the skill quality bar, or Excalidraw diagrams. Route to exactly one subskill per subdomain; fan out subagents when a task spans several. Triggers: "hold this to the engineering bar", "is this code readable", "review these tests", "untangle these dependencies", "diagnose this", "flaky test", "clean up this refactor", "document this service", "audit the docs", "review this skill", "draw a diagram".
基于 SOC 职业分类
