Describe a refactor, start it in the evening, and review a stack of small commits in the morning. Unattended Refactor plans the work as small steps, runs your tests after each one, and stops instead of guessing when something fails.
Usage
Commit your work first: it starts from a clean working tree on a new branch.
Start Refactor night and describe the goal ("move the date helpers into one module and update the callers").
Check the plan it proposes, then let it run.
In the morning, read the report and keep, reorder or drop commits.
What it produces
A branch refactor/<date> with one commit per step, each revertible on its own
REFACTOR-REPORT.md: every step with its diff summary and test result, and anything it skipped
Configuration
testCommand (default: detected from the project): runs after every step; a failing step is reverted and noted.
maxSteps (default 40) and maxFilesPerStep (default 6) keep the changes reviewable.
scope: the paths it may touch; nothing outside them is edited.
Notes
It never pushes and never rewrites existing history.
