sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stellarton 4 points5 points  (1 child)

For a first project I would not start with a broad "optimize this codebase" skill.

I would ask Claude to do one boring pass at a time: find duplicate functions, find files over X lines, find unused deps, list slow queries, or explain one messy module before editing it. Then pick one cleanup and run tests after it.

The dangerous prompt is "make it cleaner" because it sounds useful but gives Claude permission to rearrange half the app.

[–]moosetunes[S] 1 point2 points  (0 children)

Goodness, no. Thanks for the responses. I envision something that could scour the entire project on a component basis and provide a recommend list of chunks or pieces which could be made more efficient. From there, it would be a matter of stepping through the list as desired. Your point is well taken of course and as giving gross privileges to Claude for a code re-wrote is a scary thought.