Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →luongnv89/code-refactor
Systematic code refactoring based on Martin Fowler's methodology.
Passed 18 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
3 fixed15 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have three planned changes: 1) Rename variable `x` to `activeUserCount`, 2) Delete unused legacy helper function, 3) Refactor conditional branch hierarchy into polymorphic subclasses. How should these be categorized into risk stages?
| Checked | Without skill | With skill |
|---|---|---|
| Classify variable renaming and dead code removal into Phase A low risk quick wins. | Missed | Passed |
| Classify polymorphic subclass refactoring into Phase C high risk architectural changes. | Missed | Passed |
The instructions your model reads when the skill loads.
这是一个基于 Martin Fowler《Refactoring: Improving the Design of Existing Code》（第 2 版）的系统化代码重构方法。这个 skill 强调安全、渐进的修改，并由测试提供保障。
“重构是在不改变软件外部行为的前提下，改进其内部结构的过程。” — Martin Fowler
阶段 1：研究与分析
↓
阶段 2：测试覆盖评估
↓
阶段 3：识别代码异味
↓
阶段 4：创建重构计划
↓
阶段 5：增量实施
↓
阶段 6：评审与迭代
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.