菜单
Refactor code safely in small, verifiable steps while preserving external behavior. Use when user says "refactor", "clean up this code", "simplify", "improve readability", "remove dead code", or asks to restructure without changing functionality.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | refactor-safe |
| description | Refactor code safely in small, verifiable steps while preserving external behavior. Use when user says "refactor", "clean up this code", "simplify", "improve readability", "remove dead code", or asks to restructure without changing functionality. |
| disable-model-invocation | true |
Refactor the requested code while preserving external behavior.
Improve one or more of without changing functionality:
Target
- <files / symbols reviewed>
- Goal: <why this refactor is worth doing>
Plan
1. <small step>
2. <small step>
Changes made
- <concrete change>
Behavior preserved
- <what intentionally stayed the same>
Verification
- <tests / build / checks run and result>
Risks / follow-ups
- <remaining concern or "None significant">
Orchestrates the full idea-to-ship workflow. Use when the user has a new idea, feature, or project and wants guided step-by-step progress. Triggers on "I have an idea", "let's build", "new feature", "start a project", or when the user wants to follow the complete workflow from concept to code.
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Self-driving version of grill-with-docs. Runs an auto-grill loop (auto-selects recommended options without asking) while creating ADRs and glossary entries via domain-modeling as decisions resolve. Use when the user says "auto-grill with docs", "grill and decide with docs", or invokes /grill-with-docs-auto.
Long-running iterative development loops with pacing control and verifiable progress. Uses .scratch/<plan>/ structure where each plan has a PRD.md and issues/. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.