Project Leader
The branch that's waited six days for review tops today's list
Reads the diff on every branch that diverged from main and posts a daily queue: what each change does in two lines, its size, and how long it has waited.
Changes waiting for review are where momentum goes to die, and the queue is invisible by default: no dashboard shows the branch that has been ready since last Tuesday quietly going stale against main.
How it works
- 01
With the repository in its workspace, the agent checks on a schedule which branches have diverged from the main line, reads the diffs, and works out what each change actually does. The daily summary, delivered to Slack, Microsoft Teams, or email, lists every pending change with a two-line plain-language description, its size, days waited, and whether it has drifted stale, oldest items at the top instead of sunk out of sight. Reviewers can pick work from the summary without checking anything out, and branches you have told it to ignore stay ignored, so spikes and experiments do not pad the list.
- 02
A desk table tracks the queue over time, which is where the slow rot shows: when the average wait creeps up week over week, you see it in the table before anyone is annoyed enough to say so.