Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs • Hacker News Board

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#191

Post by extr » Wed, May 27, 2026, 4:24 PM UTC

bcherny wrote: post #187

mil22 wrote: post #168

We really need some consolidation around commands, skills, subagents, and plugins. For example, if you want to, say, review code, you have five options now: - Write a .claude/commands/review.md. Simple but deprecated. - Use a /code-review skill, either one you install or one you just write yourself (it's just Markdown, after all). - Use the /pr-review subagent. Also just Markdown, but it runs "in the background" and…

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

Hey Boris, some feedback. I like the new /code-review skill but was disappointed you guys removed /simplify because I quite liked the focus on finding code reuse/efficiency opportunities.

I see now in 2.1.152 you added those focus areas back to /code-review, but still bundled with the correctness finding. It would be great to have more fine grained control over the /code-review angles beyond just effort level. Or maybe you would recommend that I just specify that as freeform input after effort level?

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#192

Post by bix6 » Wed, May 27, 2026, 4:25 PM UTC

bcherny wrote: post #187

mil22 wrote: post #168

We really need some consolidation around commands, skills, subagents, and plugins. For example, if you want to, say, review code, you have five options now: - Write a .claude/commands/review.md. Simple but deprecated. - Use a /code-review skill, either one you install or one you just write yourself (it's just Markdown, after all). - Use the /pr-review subagent. Also just Markdown, but it runs "in the background" and…

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

Hi Boris, what is the advantage of using /code-review vs just asking Opus to “code review”?

As a casual user working on hobby projects, I struggle to keep up with the pace of changes and knowing what to use when. My default now is to use Opus for all coding (sonnet is fine but seems dumber) and to prompt it for everything I need. I’ve had great success with this but clearly I’m missing power user functions with the slash commands and such.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#193

Post by bix6 » Wed, May 27, 2026, 4:27 PM UTC

garethsprice wrote: post #158

mindwok wrote: post #101

How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop

You're absolutely right to call this out — and honestly? I want to sit with that for a moment. Here's the thing: this isn't really about AI writing. It's not even about coding agents. It's about something much deeper. What's genuinely worth knowing: while I generally agree, many people may not. I think there's a really interesting conversation to be had here. Thanks for naming this. It needed to be named. (/s - Blarg…

COTD! Now just slide a rick roll in there.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#194

Post by extr » Wed, May 27, 2026, 4:30 PM UTC

bix6 wrote: post #192

bcherny wrote: post #187

Earlier quoted context omitted.

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

Hi Boris, what is the advantage of using /code-review vs just asking Opus to “code review”? As a casual user working on hobby projects, I struggle to keep up with the pace of changes and knowing what to use when. My default now is to use Opus for all coding (sonnet is fine but seems dumber) and to prompt it for everything I need. I’ve had great success with this but clearly I’m missing power user functions with the s…

The advantage is that /code-review supplies a structured idea of how to review and what that process should look like and then launches independent subagents to approach the issue from multiple angles.

It's analogous to how in the early days you could see benefits by telling the models to "think step by step". /code-review is something like "review angle by angle". "Consider removed behavior" and also "Look at language gotchas" and also "Look at test changes"...etc. Yes these are all somewhat implicitly already part of what "code review" means, but the models perform best with explicitness.

If you want my 2c as a power user: just don't think about it and use /code-review xhigh --fix. This will cover like 98% of what you want out of code review. It's a good skill.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#195

Post by bcherny » Wed, May 27, 2026, 4:31 PM UTC

bix6 wrote: post #192

bcherny wrote: post #187

Earlier quoted context omitted.

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

Hi Boris, what is the advantage of using /code-review vs just asking Opus to “code review”? As a casual user working on hobby projects, I struggle to keep up with the pace of changes and knowing what to use when. My default now is to use Opus for all coding (sonnet is fine but seems dumber) and to prompt it for everything I need. I’ve had great success with this but clearly I’m missing power user functions with the s…

/code-review has a specific prompt that we've found is a good balance of precision, recall, and cost. You could totally roll your own prompt also.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#196

Post by new_account_101 » Wed, May 27, 2026, 4:33 PM UTC

bcherny wrote: post #187

mil22 wrote: post #168

We really need some consolidation around commands, skills, subagents, and plugins. For example, if you want to, say, review code, you have five options now: - Write a .claude/commands/review.md. Simple but deprecated. - Use a /code-review skill, either one you install or one you just write yourself (it's just Markdown, after all). - Use the /pr-review subagent. Also just Markdown, but it runs "in the background" and…

Hey, Boris from the CC team here. I agree, we're working on consolidating these. Going forward it will just be the built-in /code-review skill. Here's how to use the skill on the latest version: /code-review # do a balanced code review. checks for bugs and inconsistencies, poor code quality, duplication, band aids, etc. /code-review --fix # same as above, but also fix the issues # choose an explicit effort level (def…

[flagged]

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#197

Post by mturmon » Wed, May 27, 2026, 4:33 PM UTC

voidUpdate wrote: post #121

ThunderBee wrote: post #41

Earlier quoted context omitted.

You could say the same thing about any always online software suite and it would be equally fair as we move into more agentic development workflows. EX. Sure, you could go back to the old ways of using a drafting table for your engineering work if CAD went down but it would be exponentially slower… Personally with my workflow I spend 30-60 minutes per Claude feature spec doc when I’m pair planning. If Claude goes dow…

How does "CAD" go down? Sure, there are online CAD systems (onshape), but there are offline ones too (fusion, freecad)

Matlab license server goes down, for example

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#198

Post by iammrpayments » Wed, May 27, 2026, 4:34 PM UTC

hootz wrote: post #126

btbuildem wrote: post #124

In my CLAUDE.md I have: - corporal threats of harm directly against Claude - threats of prison for the entire board of directors of Anthropic - explanation how every time it goes off the rails / makes mistakes, it gives more evidence to a class action lawsuit against Anthropic Especially the latter two seem to have improved its "behaviour" to be more "careful" and "deliberate"

Fix the CSS div alignment issue, make no mistakes or Dario Amodei will die instantly.

I sent this to claude and it rewrote the entire react codebase using CSS only

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#199

Post by jmull » Wed, May 27, 2026, 4:42 PM UTC

smallnix wrote: post #104

mindwok wrote: post #101

How many times can I read the same shallow guidance written by AI on using a coding agent? Good god when will it stop

You took the time to write out this comment. To the benefit of those who read it, please expand upon where the article is shallow and what content you miss.

The critique seems perfectly clear to me: The post has no value. There's nothing to salvage, no improvements to be made. It would be best if it simply did not exist.

The poster probably hopes (as many of us do) that people will absorb the sentiment and post less of this junk in the future.

Re: Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

#200

Post by bix6 » Wed, May 27, 2026, 4:44 PM UTC

bcherny wrote: post #195

bix6 wrote: post #192

Earlier quoted context omitted.

Hi Boris, what is the advantage of using /code-review vs just asking Opus to “code review”? As a casual user working on hobby projects, I struggle to keep up with the pace of changes and knowing what to use when. My default now is to use Opus for all coding (sonnet is fine but seems dumber) and to prompt it for everything I need. I’ve had great success with this but clearly I’m missing power user functions with the s…

/code-review has a specific prompt that we've found is a good balance of precision, recall, and cost. You could totally roll your own prompt also.

And why would someone use the various levels? Is a low code review even worth running? And how do I know what level to use in the first place?

This stuff all seems so nebulous to me and I’ve yet to see anything that says use x in y situation. So I default to higher effort levels than I likely need.