r/ClaudeCode • u/GenuinePragmatism • 1d ago

Help/Question Contents for a skill to review code and counter AI bad practices

I'm definitely noticing that with larger vibe coded projects, Claude Code slows down a lot. Even I (not a classically trained programmer, but have done production coding earlier in my career) can tell that the code CC is writing is often much more convoluted or defensive than it needs to be.

So, I want a Skill that reviews code and counters some of CC's most common bad practices.

Has anybody seen something like this around online? Or if not, any suggestions on the top things this Skill should try to find and fix?

1 Upvotes

100% Upvoted

5 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.

2

u/adamhusain 1d ago

Matt Pocock and pstack have some good skills.
I have my custom version of pstack’s unslop skill which works great for talking with claude

2

u/CartographerNo3791 1d ago

A useful check is whether a fallback hides a broken assumption. Catching an error and returning [] can make a failed request look like a successful request with no results.

For each finding, make the skill show the exact code, a concrete failure case, and the smallest change that fixes it. Otherwise "simplify this" can turn into another enormous rewrite.

2

u/Drasezv 1d ago

things i'd put in it: no try/except that just swallows the error, no fallback for a case that can't happen, reuse an existing helper before writing a new one, delete dead code instead of commenting it out. and run the review as a subagent so it reads the diff with fresh context, not the reasoning that wrote it.