Post

We made a skill for assessing the risk of merging a PR: /merge-risk This addresses the code review bottleneck by letting devs trust the agent for lower risk changes. It grades risk across 5 categories: alignment, impact, verification, rollback cost, and error detection.

20/10/26, 9:11 pm0 reposts8 likes

Nitish Agarwal

@nitishagar.bsky.social

Rollback cost is the category I'd weight heaviest. A risky change behind a flag with a one-click revert is safer to merge than a 'small' migration you can't undo. Curious how you calibrate the grades against PRs that actually caused incidents.

Ben Holmes

@bholmes.dev

Try it out: > npx skills add warpdotdev/common-skills --skill merge-risk