How the Claude Code team does code review

Re:How the Claude Code team does code review by AlexErrant on Friday October 16, 2026 @10:09PM (#50127198)

To be clear: you can certainly do "Hi, /grill-me on X" anytime you want. You can even write "hi, /grill-me and use /search-docs", even though the /search-docs skill absolutely doesn't work. But the Claude Code _harness_ won't autoload the skill into context, so claude-the-model has to go "hmm, where can I find that skill, when I call the Skill tool with that name it no worky, so now I have to search the filesystem for that skill...".

https://github.com/anthropics/claude-code/issues/92769

The <command-args> I know because I just audited my raw Claude transcripts via ccglass. You can verify by just asking Haiku "hey, /grill-me does this skill autoload for you?" and then "/grill-me hey, how many times does this text appear in your context?"

You can trivially doublecheck me. The above prompts won't even eat 1% of a 5 hr on 20$ plan.

[ Parent | on HN ]

Re:How the Claude Code team does code review by steveklabnik on Saturday October 17, 2026 @09:03AM (#50130791)

Okay, yes, I agree that that’s how it works. I thought when you said MUST you meant that it doesn’t work; it does work it’s just that it burns a turn or two to do the lookup there. I certainly agree it would be nice to not do so.

(And I didn’t know the double args thing, that’s very interesting! I should have said I only meant the first bit.)

[ Parent | on HN ]