Been wrangling a lot of time how to deal with the onslaught of PRs, none of the solutions that are out there seem made for our scale.
I spun up 50 codex in parallel, let them analyze the PR and generate a JSON report with various signals, comparing with vision, intent (much higher signal than any of the text), risk and various other signals.
Then I can ingest all reports into one session and run AI queries/de-dupe/auto-close/merge as needed on it.
Same for Issues. P rompt R equests really are just issues with additional metadata.
Don't even need a vector db. Was thinking way too complex for a while.
There's like 8 PRs for auto-update in the last 2 days alone (still need to ingest 3k PRs, only have 1k so far).
AI coding 一个实践:每次做重大功能/改动之前先用 plan mode 做一个 research / design doc,然后再基于这个 doc 做实现的 plan。
design doc 加上编号存到一个文件夹里,commit 进仓库。这就类似你的设计思路的 db migrations,记录着整个项目进化思考的脉络。