|
|
|
|
|
|
by marwamc
188 days ago
|
|
|
Nice. As a heavy claudecode user, I've ran into a certain form of this problem. My problem was: for refactoring/renaming workflows Claude seems to run grep/ripgrep to enumerate occurrences of a symbol before renaming, but somehow misses some references, especially in test files or documentation. After renaming a symbol I would have failing tests, which Claude will dutifully fix, so not the worst problem. However the out-of-date documentation references slowly bite me in the neck because in future, Claude might read the outdated docs and make false assumptions or wrong decisions. So I made an mcp tool that searches an indexed repo for all references/usages of a symbol and returns ranked results. https://gitlab.com/rhobimd-oss/shebe/-/blob/main/docs/guides... Also recently there a ShowHN about a tool called nia that does something similar. https://docs.trynia.ai/tools-features |
|
|
Yeah, that is a challenge we also faced and gave it a good amount of thought. Something like exposing LSP find references capabilities to the agent. Didn't follow this approach though ourselves.
On the documentation front, with ProdE we actually map out the features mentioned in docs to the actual code files, and diff against new commits to see if any file was edited. Edit means docs need to be updated. Working well this way.
Nia is great, but i believe they are indexing the open source world. Are they indexing private repos as well?