Should migrate all commands into skills

[tmchow]

Claude Code 2.1.3+ merged commands into skills.

From https://code.claude.com/docs/en/skills:

Custom slash commands have been merged into skills. A file at .claude/commands/review.md and a skill at .claude/skills/review/SKILL.md both create /review and work the same way. Your existing .claude/commands/ files keep working. Skills add optional features: a directory for supporting files, frontmatter to control whether you or Claude invokes them, and the ability for Claude to load them automatically when relevant.

Given this, I think there's no real downside. Boris says (emphasis mine):

Skills are usually invoked by the model, slash commands by the user. But as we see people write more and more of each the line honestly gets pretty blurry. We think the model will do most of the invocation soon and are simplifying the system a bit in prep for that.

Also skills supports disable-model-invocation and user-invocable to control visibility and invocation if we needed to more granularly control that.

So I think it makes sense to just get ahead of this and move all the commands into skills.

[Joshua-IQ]

I'm using the compound engineering plugin today and I actually quite like being able to /slash-command it seems more predictable than remembering and invoking the right skill. Claude is not good at organically noticing when to use skills or not yet.

[tmchow]

I'm using the compound engineering plugin today and I actually quite like being able to /slash-command it seems more predictable than remembering and invoking the right skill. Claude is not good at organically noticing when to use skills or not yet.

Skills can be used as slash commands thought.