菜单
Refactor code without changing behavior. Use when the user asks to clean up, simplify, rename, restructure, extract, inline, move code, reduce duplication, or modernize internals while preserving behavior. Produces a scoped refactor with before/after checks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ariaxhan/the-agent-library --skill refactor-code-safely命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Turn a borrowed metaphor, analogy, or cross-domain inspiration into a testable mechanism, or prove it is decoration and discard it. Use when a design leans on language from another field ("immune system", "evolution", "market", "quorum", "crystallization"), when someone proposes copying how another domain solves a problem, or when reviewing a system whose names sound deeper than its code. Produces either a named domain-free invariant with evidence and falsifiers, or an explicit rejection with the reason it failed.
Design systems so a failure can never present as success. Use when building or reviewing pipelines, extractors, reconciliations, checkers, or any computation whose output humans act on; when missing inputs, unreadable files, or crashes could pass silently; when a tool "found" an explanation that feels too convenient; or on "make this fail loudly", "could this lie to us", "harden the failure paths". Produces named invariants, explicit skip and no-answer states, honest cause classes, and adversarial regression fixtures.
A compact decision protocol for non-trivial choices, reviews, governance calls, and live disagreement. Use implicitly at decision points, even when nobody says "debate", whenever a choice is high-impact, hard to reverse, policy-bearing, or has multiple plausible paths that evidence alone cannot settle. Skip for trivial, cheap-to-reverse, or deterministically decidable choices.
基于 SOC 职业分类
正在显示 SKILL.md
| name | refactor-code-safely |
| description | Refactor code without changing behavior. Use when the user asks to clean up, simplify, rename, restructure, extract, inline, move code, reduce duplication, or modernize internals while preserving behavior. Produces a scoped refactor with before/after checks. |
Refactoring changes structure, not behavior. If behavior changes, it is a feature or bug fix, not a refactor.
Run the nearest relevant tests or checks before editing. If no tests exist, identify how current behavior will be preserved.
For risky code, create temporary characterization tests: tests that capture what the code does now.
Find every instance of the symbol, pattern, module, route, or component involved. List the intended scope before editing.
If the change touches many files, split it into smaller transformations.
Choose one:
Do not mix unrelated transformations.
Keep edits mechanical and boring. Avoid opportunistic improvements.
Rules:
Run the baseline checks again. For behavior-sensitive code, compare old and new outputs on the original input set.
If checks fail, stop and fix or revert the last transformation before continuing.
Return:
