Inject file-specific context into new or edited files as comments

[ericfitz]

Note: this is subtly different than other "add context for" asks - I am not asking to bring external data into the current session context, I am asking to inject context into files as comments

LLMs have a tendency to lose or minimize early context in long sessions.

However, the file-based nature of working with source code gives a unique ability to refresh context frequently, as files are frequently read.

I would like Roo Code to automatically add little bits of context to any file it's editing or generating, in the form of comments, if the file format permits comments.

For example, I have a typescript project that uses Vitest for unit testing, Cypress for integration/e2e testing, and I don't use jasmine or jest anywhere, nor do I use jasmine format even though there's some compatibility in vitest. In longer sessions fixing broken tests or implementing new tests, over time both Sonnet and Gemini (especially Sonnet) will start using jasmine format.

It would be awesome if when Roo Code uses the LLM to create or edit each .spec.ts file for the first time, it added a comment like:

/******
* unit test for auth service component
*
* additional context:
*     run this test only: pnpm run test "<relative path to this test file, including file name>"
*     unit tests only use vitest syntax; no jasmine or jest
*     do not disable or skip failing tests, ask the user what to do
******/

Roo would need some UX for the user to configure what bits of context go into such context for different file types.