Warp

Ben Holmes Verified account @BHolmesDev · 3d

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.

View quoted post on X

sathvik Verified account @vikvang1 · 4d

It’s coming together and coming soon 😊

Manage your software factories entirely from your iPhone

Benchmarks, metrics, model routing, teams, integrations, and everything in between

View quoted post on X

Ben Holmes Verified account @BHolmesDev · 4d

Alright, it's time to address the code review bottleneck.

Here's 3 steps worth adding to your agent workflows:
1. Build your own code review loop
2. Verify flows end-to-end with simulated environments
3. Score and mitigate risk with /merge-risk x.com/i/article/2118…

View quoted post on X

Zach Lloyd Verified account @zachlloydtweets · 5d

I often see tweets that a software factory can be built with a string of prompts tying together cloud agents. My experience is that this is false.

Companies often start there and regret it because it doesn’t scale. x.com/i/article/2117…

View quoted post on X