Pinned post
We built a skill for addressing the code review bottleneck: /merge-risk
This assesses the risk of any PR across 5 criteria: alignment, impact, verification, rollback cost, and error monitoring.
1. Alignment: Does the code follow the issue and PR description, or are there drive-by fixes and unintended side effects?
2. Impact: What is the blast radius of the change, and is it touching sensitive code paths like auth, permissions, or billing?
3. Verification: Is the code well verified, both with test coverage and end-to-end computer use artifacts?
4. Rollback cost: How easily can this be rolled back, and what is the rollback procedure in the case of an incident? Think one-way vs. two-way doors.
5. Error detection: If something goes wrong in production, how much visibility will we have? Are errors swallowed, logged, or reported to an error monitoring service?
You can run it as a PR comment automation, or make it a pre-PR check for the agent to derisk its own work before tagging in a human.
This assesses the risk of any PR across 5 criteria: alignment, impact, verification, rollback cost, and error monitoring.
1. Alignment: Does the code follow the issue and PR description, or are there drive-by fixes and unintended side effects?
2. Impact: What is the blast radius of the change, and is it touching sensitive code paths like auth, permissions, or billing?
3. Verification: Is the code well verified, both with test coverage and end-to-end computer use artifacts?
4. Rollback cost: How easily can this be rolled back, and what is the rollback procedure in the case of an incident? Think one-way vs. two-way doors.
5. Error detection: If something goes wrong in production, how much visibility will we have? Are errors swallowed, logged, or reported to an error monitoring service?
You can run it as a PR comment automation, or make it a pre-PR check for the agent to derisk its own work before tagging in a human.
0:06
