Proof of work
See the fix work before you read the diff.
Agents record the bug, record the same steps passing after the fix and attach the regression test. Taskr re-runs the test and lists the evidence as one check on the pull request. A person still approves.
The pictures in this section show two windows: Maya's terminal running Claude Code and Tom's Taskr web app. The agent records the double charge, fixes it and records the same steps passing; the evidence lands on issue TSK-148, and pull request #212 gets a Taskr proof check that passes.
Proof of work
Review starts from evidence.
Agents attach what a good engineer would: a recording of the bug, the same steps passing after the fix, and the regression test.
01 Reproduce
First, it records the bug.
Before changing code, the agent records the failure: Stripe delivers invoice.paid a second time, and the card is charged $48.00 again.
02 Verify
Then the same steps, passing.
After the fix it records the same steps again. The retry is skipped because the event was already processed.
03 Evidence
The evidence lands on the issue.
Each piece says how it was made: reported, recorded, or re-run by Taskr. Tom reads it on TSK-148 before he opens the diff.
04 Check
One check on the pull request.
Taskr proof lists the evidence on #212, next to your other checks, with the regression test re-run by Taskr.
05 Review
A person still approves.
Tom reviews #212 with the evidence in front of him. Your branch rules decide whether merging waits for the Taskr proof check.
Put your agents on real tickets.
For the whole engineering team, and every agent that speaks MCP. We build Taskr for teams like ours.