how do you clean up dead code and unused components after a fast vibe coding sprint?
by•
after spending two nights rapidly testing different layouts and API helpers, my project folder always ends up full of orphaned files and half-used utility functions that nothing imports anymore.
asking the agent to delete unused files feels risky because it sometimes removes dynamic routes by mistake.
what tools or habits do you use to tidy up a messy repo once the prototype actually works?
12 views
p/nudgeforme
p/nexupira
p/runevr
p/producthunt
p/google-cloud-platform
p/many-displays
p/operum
p/murror
p/dino-kids
p/tabstack
p/any-video-to-text
p/rithub
p/seldon
p/jot-2-0
p/okapi-2
p/gatrends
p/kodlo
p/appxiom
Replies
I'd trust your gut there. One rule my agents follow word for word is that "not used" doesn't mean "safe to delete". They only delete what I name explicitly, and anything whose purpose isn't clear stays untouched. Before deleting anything they copy it under another name first.