Refactor skill
Benchmark, lint, and standardize reusable skills for AI coding agents.
npx -y skills add ChristinaAgent/OpenSkillBench --skill refactor-skillAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Refactor existing code while preserving behavior, tests, public contracts, and local project conventions.
SKILL.md
1.9 KB, as published. Nobody here has run it
Refactor Safety Skill
Use this skill when the user asks for a behavior-preserving refactor.
Procedure
- Identify the behavior and public contracts that must stay unchanged.
- Inspect existing tests and local style before editing.
- Keep the refactor narrow and avoid opportunistic behavior changes.
- Preserve names, exports, data formats, and error behavior unless requested.
- Run focused tests or document the verification gap.
- In the final response, separate what was reorganized from what behavior remained unchanged.
Output Shape
Explain the structural improvement, the unchanged behavior, and the verification performed.
Gives 0 of the 12 instructions most refactoring skills give
Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06
- run tests after each changein 59 of 521, across 56 files
- write tests before refactoringin 27 of 521, across 24 files
- preserve external behaviorin 26 of 521, across 22 files
- remove dead codein 25 of 521, across 24 files
- make small incremental changesin 20 of 521, across 17 files
- break the implementation into tiny commitsin 18 of 521, across 5 files
- ask the user about alternative optionsin 17 of 521, across 4 files
- create a GitHub issue with the planin 17 of 521, across 4 files
- explore the repository to verify assertionsin 17 of 521, across 4 files
- interview the user about the refactorin 16 of 521, across 3 files
- check the codebase for test coveragein 16 of 521, across 3 files
- refactor one thing at a timein 16 of 521, across 12 files
Said here and by no other author read
- identify unchanged behavior and public contracts
- inspect tests and style before editing
- keep the refactor narrow
- avoid opportunistic behavior changes
- preserve names exports formats and error behavior
- run focused tests or document verification gap
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.