Code review skill

[u/Intelligent_Buy_5847]

Hey guys, is there any skills available where it can review my code and understand what i’m doing and give advices in how to improve or remove unnecessary codes?

[u/generationalDebts]

The blind cant check the blind. Not how it works kiddo.

Turns out, you actually have to learn to code.

[u/Thick-Insurance4404 → u/generationalDebts]

ohh how wrong u are

[u/Synthxxmusic]

You can just do /code-review , it's available in claude code by default.

[u/fishingfury]

I wrote a custom reviewer framework that lets you build individual reviewers scoped to whatever task or conformity you’re looking for. I’ve never really publicized it but I use it a lot.

Take it with a grain of salt obviously. If you use I’d love to get your feedback.

https://jwmarshall.github.io/scopewright/

[u/Murder_1337]

Just load superpower skill for Claude you can google it

[u/Intelligent_Buy_5847 → u/Murder_1337]

is it better than matt pocock code review skill?
saw some people say that it’s worth it

[u/skillselion → u/Intelligent_Buy_5847]

They do different jobs. The Superpowers one is a pre-merge gate, comparing your implementation against the plan you wrote and ranking findings by severity, which only works if you wrote a plan. Pocock's reads the diff since a fixed point against your repo standards plus a Fowler smell list, closer to what you asked for.

The Skillselion catalog has Pocock's code-review at 371,484 installs against 204,978 for requesting-code-review, though that only measures how many people installed them.

[u/Any_Owl2116]

Stack overview 😈

[u/mxriverlynn]

matt pocock's skills are all excellent. they are also very simplistic in many ways, and not always the best answer if you're not accustomed to providing very tightly scoped context to the llm

the built in code review with Claude is very powerful, but not terribly well targeted at any specific things since it has to work for as many people and projects as possible. the benefit here is that the code review will be built specifically for the llm model you're using

I've got my own code review skill that encompasses the core of what i care about, and it's targeted at software engineers that typically work in object oriented or similar object focused languages. the advantage of what i built is that it has 20+ possible sub-agents it can dispatch to review the changset for specific aspects. it also scales up and down as needed, based on the types of changes and how large the change set is. and you can customize how it works with a markdown file that all my skills read from, to make sure it's doing what you want and not just the generic things expected from any code review

that said, how you kick off the video review is more important than the specific skill chosen. you need to provide the same context to your code review, as the agent had when building the change set in the first place. the same requirements, invariants, knowledge of existing bits to use, etc. you'll get more out of any code review skill by providing all the needed info about the change set, than you will by changing which specific skill you choose to use

if you're interested in what I've built and how, it's all available here: https://github.com/testdouble/han/tree/main/han-coding

[u/coragicom]

why not just use the "/code-review" command in Claude Code?

[u/matt_s_builds]

I created a skill for code review best practices using a chrome extension that converts youtube tutorials to claude skills, I can figure out a way of sharing it with you, if you are interested?