|
|
|
|
|
by daemonk
91 days ago
|
|
Yeah this is the simpler and also effective strategy. A lot of people are building sophisticated AST RAG models. But you really just need to ask Claude to generally build a semantic index for each large-ish piece of code and re-use it when getting context. You have to make sure the semantic summary takes up significantly less tokens than just reading the code or its just a waste of token/time. Then have a skill that uses git version logs to perform lazy summary cache when needed. |
|