The code shipped on Tuesday, but the task still says in progress. After a merge, the board just doesn't get updated.
Ask the agent in your editor — it already has the repository open and is signed in to GitHub. It matches commits and pull requests to Timestripe tasks, adds review links, updates delivery stages, and marks milestones complete.
What the agent starts with
An Engineering board with four tasks still in Doing, and a repository where three of those four have already shipped.
There is nothing in between. The agent reads the commits and the pull requests where they already are.
The four are not the same shape, and that is the point:
- Two were merged through pull requests, and their commit messages carry the task ID.
- One went straight to
mainas a single commit, no pull request, ID in the message. - One exists only on a branch that was pushed and never merged.
The prompt
Two of the four rules are about what not to do. They are what makes the rest safe to run unattended.
What comes back
Three tasks closed, each with a comment holding the evidence.
Where there was a pull request, the comment links it alongside the commit. Where the work went straight to main, the comment says so — PR: none (direct commit) — and gives the commit and the merge date instead.
The branch task stayed in Doing. The commit exists, the work looks done, but it was never merged into main, so by the rule it isn't. A task about a staging 401 stayed in the Inbox — a recent commit adds a regression test for it, which is close but not the same thing. That one came back in the reply as something to confirm rather than something to close.
The agent wrote nothing on either of them. It doesn't leave a note on a task it isn't sure about.
