donaldfilimon/abi / .agents/skills/refactor
refactor
VerifiedPlan, execute, and validate a codebase modernization or refactor with clean-slate thinking while preserving semantics. Use when the user asks how to approach a rewrite vs incremental change or what the risk is (strategy), is ready to apply a refactor plan safely (implementation), or asks whether a refactor broke anything or is complete (validation).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.7 KB |
| references/implementation-playbook.md | markdown | 3.0 KB |
| references/strategy-guide.md | markdown | 1.3 KB |
| references/validation-checklist.md | markdown | 912 B |
references/validation-checklist.md
View on GitHub# Refactor Validation Checklist
Use before declaring any modernization complete.
## Behavioral Parity
- [ ] All original tests still pass
- [ ] New characterizing tests added for key paths
- [ ] Manual scenarios from original behavior verified
- [ ] Contracts / public API surface unchanged (or intentionally evolved with docs)
## Modern Quality
- [ ] Modern patterns applied (see modern-patterns skill)
- [ ] Error handling is explicit and typed where appropriate
- [ ] No silent failures or broad catches
- [ ] Code is easier to read and reason about
- [ ] Observability / logging improved or maintained
## Structural
- [ ] Clear module boundaries
- [ ] No god objects or excessive coupling
- [ ] Documentation and types reflect the new design
- [ ] Dead code from old approach removed (after cutover)
Run the validation skill plus a Rust-aware `abi` or `refactor-planner` agent
review as the final step.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |