Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.
Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct.
npx skills add https://github.com/DevelopersGlobal/ai-agent-skills --skill refactoring이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
| name | refactoring |
| description | Safe, behavior-preserving code transformation backed by tests. Refactor with evidence, not instinct. |
| category | review |
| applies-to | ["claude","gemini","cursor","copilot","any"] |
| version | 1.0.0 |
Refactoring changes the internal structure of code without changing its external behavior. The keyword is "without" — if behavior changes, it's not refactoring, it's modification. This skill enforces safe refactoring with tests as the safety net.
Verify: Tests pass. They cover the code being refactored.
Verify: Tests pass after every individual change.
Verify: This commit does exactly one type of refactoring.
Verify: All tests pass. No observable behavior change.
| Excuse | Rebuttal |
|---|---|
| "I'll add tests after refactoring" | You can't verify a behavior-preserving refactor without tests before the refactor. |
| "This change is obviously safe" | Obvious safety is how production incidents happen. Run the tests. |
| "I'll just do a quick cleanup" | "Quick cleanup" that changes behavior is a bug, not a refactor. |
Automated quality gates from commit to production. Every merge to main is potentially shippable. No manual steps in the deployment path.
Document decisions, not just implementations. ADRs for architectural choices, inline docs for non-obvious code, and runbooks for operational knowledge.
Graceful degradation and meaningful error messages. Errors are first-class citizens, not afterthoughts. Every error path is designed, not discovered.
Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
Distill complex topics into layered, actionable summaries. Start with the key insight, layer in detail, end with recommended next action.
