We have the @ codebase feature for asking high-level questions about a codebase, but this doesn't cover the cases where you want the LLM to see literally every file (e.g. code review).
Probably every programmer could benefit from at least being able to specify a custom prompt and having the LLM watch over their git diff periodically to look for improvements.
An MVP of this feature might look like:
a) configuration in config.json to set the review prompt
b) a file save listener, polling loop, or button to automatically trigger a review
c) the actual reviewing logic: probably loops through each file or portion being reviewed, applies the prompt, and gets feedback from the LLM
d) display for this feedback. Perhaps makes sense as another page in the sidebar (gui/src/pages)
We have the @ codebase feature for asking high-level questions about a codebase, but this doesn't cover the cases where you want the LLM to see literally every file (e.g. code review).
Probably every programmer could benefit from at least being able to specify a custom prompt and having the LLM watch over their git diff periodically to look for improvements.
An MVP of this feature might look like: a) configuration in config.json to set the review prompt b) a file save listener, polling loop, or button to automatically trigger a review c) the actual reviewing logic: probably loops through each file or portion being reviewed, applies the prompt, and gets feedback from the LLM d) display for this feedback. Perhaps makes sense as another page in the sidebar (
gui/src/pages
)