[samrolken]

I've been maintaining my own script that does something like this. A few things I've found to be useful: It can also pull in context from git history (prioritize based on which files have been most recently worked on, include recent git commit messages which can help the LLM know more about what's going on), and optionally it can go do multiple stages... for long files, first summarizing them, then including the summary in the final prompt.

[aerugo_]

Interesting! Did you publish it? It’s a great idea to prioritize based on git history.

As for multiple stages, it means the tool itself is doing a few calls to the model. What do the code summaries look like? Just function and class doctrings? Getting the model to write summaries that are comprehensive enough to guide development but still more compact than the code itself seems like it may not be a trivial problem.