Earlier quoted context omitted.
The problem isn't giving MORE context to an agent, it's giving the right context These things are built for pattern matching, and if you keep their context focused on one pattern, they'll perform much better You want to avoid dumping in a bunch of data (like a year's worth of git logs) and telling it to sort out what's relevant itself Better to have pre-processing steps, that find (and maybe summarize) what's relevan…
"You want to avoid dumping in a bunch of data (like a year's worth of git logs) and telling it to sort out what's relevant itself" So instead you give it a years worth of changelog.md? "Better to have pre-processing steps, that find (and maybe summarize) what's relevant, then only bring that into context" So, not a list of commits that touched the relevant files or are associated with relevant issues? That kind of "p…
And no, I wouldn't ever give it a year of changelog.md. I give it a short description of the current functionality, and a well-trimmed list of 'lessons-learned' (specific pitfalls/traps from previous work, so the AI doesn't have to repeat them)
If you think git logs are a good way to give context, try it and and see how it works! My instinct's that it won't work as well as a short readme, but I could be wrong. It's so easy to prototype these days, no reason to not give it a shot