How I Use Unspent Tokens
6 hours ago
- #developer-tools
- #automation
- #refactoring
- Built continuous-refactoring for simple, incremental refactoring with a loop that validates changes through tests before keeping them.
- Addresses accumulated low-priority cleanup tasks (e.g., dead branches, outdated names, complex tests) that degrade repo quality but aren't urgent enough for dedicated sprints.
- Uses test suite as guardrails to allow small, safe changes, ideal for using expiring model credits on janitorial tasks like simplification or deletion.
- Introduced taste.md files to customize refactoring preferences, with versions and upgrade paths (e.g., taste --upgrade, taste --interview, taste --refine) to avoid discarding existing settings.
- Added a routing step to handle larger refactors via a migrations workflow with planning, phased execution, wake-up rules, and human review to prevent endless looping on unready tasks.
- Kept the original one-shot cleanup loop intact, with migrations opt-in (init --live-migrations-dir) to preserve simplicity while expanding capabilities.
- Developed iteratively from a basic cleanup tool to include taste management and larger refactoring support, focusing on continuous improvement over one-time impressive changes.
- Aims to make repo tidiness a background habit, converting expiring credits into maintenance work instead of letting them go unused.