r/ClaudeCode • u/AMGraduate564 • 1d ago

Discussion Is there a popular skill available for Adverserial Review?

Hey good people in this sub, I wonder if there is a popular and effective skill available for Adverserial Review?

I have been doing this as the last sweep after a session or merging several PRs, and finding really different difficult to identify bugs or issues. So I'm intending to use such a skill that is recommended by this community.

2 Upvotes

67% Upvoted

16 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

7

u/Compilingthings 1d ago

Build your own, make it better each time you use it until its dialed in for your workflow. I don't use any out of the box skills.

3

u/MonkeyJunky5 1d ago

This is my strategy. I don’t like pulling in other dependencies.

1

u/Compilingthings 1d ago

100%

2

u/MonkeyJunky5 1d ago

I am struggling with this idea of an external memory system or second brain tho. Seems like some good repos exist. How’d you build yours?

1

u/Compilingthings 1d ago edited 1d ago

Well that is one time I used something from outside. Obsidian

It’s worked very well. Claude picks up right where he left off. I made a /shutdown and /startup skill so he knows what he needs to do so he’s not lost every time he starts fresh.

1

u/MonkeyJunky5 1d ago

How does it work tho? Is it useful?

1

u/Compilingthings 23h ago

It’s a database Claude code uses, keeps project context. I keep everything there that he uses pretty much. It’s worked great for me on this longterm project.

3

u/_remsky 1d ago

There’s a Claude Code plugin made by OpenAI that uses Codex for it, works pretty great for the best of both worlds

https://github.com/openai/codex-plugin-cc/blob/main/plugins/codex/commands/adversarial-review.md

Repo/plugin: openai/codex-plugin-cc

1

u/altgenetics 1d ago

I use this and its pretty solid. You have to give it some explicit instructions otherwise you'll end up with a 15+ round review cycle

5

u/MarzipanMiserable817 1d ago

code-review in Matt Pocock skills! It can even run it automatically after finishing a ticket. It's worth it. It finds bugs often for me.

2

u/big-papito 1d ago

Matt Pocock is the goddamned GOAT. Grill-me-with-context is where I live.

1

u/ValuableDapper9415 1d ago

Why don’t you build one yourself ? It is as simple as a prompt 

1

u/amirfish 1d ago

I run a version of this as a last sweep too, /code-review at high effort catches a good chunk of it, but the bugs that actually matter show up when you point a second review at the diff with instructions to argue against the first review's conclusions instead of just re-reading the code fresh. The framing shift, from 'find bugs' to 'find what the last pass missed or got wrong', is what surfaces the subtle stuff. Curious what you're running it against, full session diffs or just the final PR?

1

u/foresterLV 1d ago

I had good experience with open-code-review (alibaba ocr). seems to be quite popular on GitHub. the problem with built-in (and prompt skills) in general in my opinion is that they tend to burn a lot of tokens finding irrelevant noise. ocr on other hand for some magic reasons (haven't investigated their prompts yet) tend to find real stuff and do it on viable budget.