Refactoring Sourcegraph Cody Code for Production

In large codebases, Cody-assisted refactors may make changes consistently within one package but miss usages in other packages that are less commonly modified. The code graph helps but doesn't guarantee complete coverage of all call sites in a very large codebase

Use Sourcegraph's search capabilities to verify all call sites of changed APIs after a Cody-assisted refactor. Run the full test suite, not just affected tests. Use compiler errors (for typed languages) as a final check for missed call sites

Not all Sourcegraph Cody code needs refactoring. If it works, is secure, and you don't need to modify it, leave it alone. Refactor when: you need to add features and the current structure makes it difficult, bugs keep appearing in the same area of code, or onboarding new developers takes too long because the code is hard to understand.

The golden rule of refactoring: behavior stays the same, structure changes. Before refactoring any code, make sure you have tests covering the current behavior (or add them first). Refactor in small steps — change one thing at a time and verify the app still works. Use version control (git) to commit after each successful change so you can revert if something breaks.

A well-organized project has a predictable structure where anyone can find what they're looking for. Group files by feature (not by type), keep related code together, and use clear naming. Every file should have a single clear purpose. If you can't describe what a file does in one sentence, it's probably doing too much and should be split.