Untangle /goal for spaghetti code
Months of vibe coding left the code in knots: an HTML wiring diagram, the worst numbered in red, then fixes tested one by one.
1.7K saves on X, as of
/goal Untangle the knotted code in this repo: leaky abstractions, copy-paste that has drifted apart, temporary workarounds that never got deleted, and empty wrappers. First, draw a wiring diagram that fits on one screen, as an HTML page: a line from each feature to every file it touches, with the worst knots marked in red and numbered. For each one, give the file, the line and how to untangle it.
Then, on a new branch, untangle them starting with the worst. After each one, run the tests and the build (if there are no tests, at least make sure the build passes), and if anything fails, roll that one back. Don't push, and don't merge. At the end, give me one comparison image: before on the left, after on the right.Use it
Send it to Codex in your repo.
You get A wiring diagram, then fixes on a new branch, any that fail rolled back, and a before/after image.
Completely untangle the spaghetti code months of vibe coding left behind.
Add Copybook to your agent, then ask it next time. Set it up
