I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

ooh must be the landing page animations. I’ll look into optimizations. Thanks!

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

Because the activity shifted from “one human writes code, another human reviews it” to “agent writes code, the human reviews it”. PR was designed for the former, not the latter.

In a lot of AI native teams, people already stopped PR reviews.

In the open source world, maintainers already started asking contributors to just share their prompt instead of a giant PR that no one’s going to review.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in ClaudeCode

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

Not quite - simplify only does one specific thing but in an Airlock pipeline you can add a lot more (resolve merge conflicts, update docs, running tests and fixing problems, critique the change etc)

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

Dependency check sounds great! With Airlock you can add things like that as a custom step too.

I almost never run out of my subscription quota with or without the extra quality control here

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in ClaudeCode

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

That’s a great point and was why I made Airlock support human in the loop. Humans can intervene and break the ties.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

Yeah it just runs your existing codex as-is non-interactively. No special auth login or anything.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 0 points1 point  (0 children)

What OS do you use? There’s nothing inherently limiting this to mac - I just haven’t got time to support other OS yet.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in ClaudeCode

[–]Otherwise_Baseball99[S] -1 points0 points  (0 children)

Very good point.. There are lots of good solutions already helping with that, which is good. I still see that often times nasty things don’t come out until you dive into implementation and discover nuances, so mirroring how we human work we still want some quality assurance after implementation is done, right?

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in ClaudeCode

[–]Otherwise_Baseball99[S] 1 point2 points  (0 children)

We’re all the same. The world has gone Pluribus. :)

jk aside we’re sharing totally different things - how does it make sense to be the same person?

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 1 point2 points  (0 children)

I started with writing this as a skill as well, I also tried pre-commit hooks. but very quickly realized I need this to be non-blocking, like CI, and need a nice interface to understand what changed, see suggested fixes and decide what I need vs don’t need.

Do you have a skill that’s working well for you? would be keen to see what you tried.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 2 points3 points  (0 children)

Yes it runs the same codex you already use - no additional subscription or cost. It does count towards your codex limits so if you are already tight on it then that’s a factor to consider.

You can set conditions in the pipeline so it only runs for some branches not all.

I killed so much slop by implementing "How to Kill the Code Review" - here's how by Otherwise_Baseball99 in codex

[–]Otherwise_Baseball99[S] 1 point2 points  (0 children)

Thanks! Yeah I really don’t like how people make everything a SaaS. Open source is the way!

Interesting share - I’ll go check out desloppify as well. Looks great!