Master Branch Context Injection

Feature Requests
1

Here’s a really common workflow I find myself executing with Cursor:

  • I modify an existing feature
  • I break the test
  • I plug the file and it’s test into Cursor’s context and ask it to update the test

In truth I find this is really hit or miss, but bringing this up with other engineers we all use this and all agreed that the thing that would help this workflow succeed would be the ability to include both the modified version of the file along with modifications when asking Cursor to update the test. Or in other words, the agent would benefit from seeing committed changes that differ from the latest master branch.

Not sure how you’d go about this, but I think this would be helpful for a lot of common workflows.

That being said, maybe this should actually be implemented as an MCP server vs. natively, although some non-power-users will never use it if that’s the case.

2

Interesting approach, wouldnt the common case be that when changes are made that also the test is changed?

Not sure if i understand how this is affected by your process.