This guide organizes Claude Code's 90+ slash commands by real-world operational use case, not alphabetical order. Learn which commands streamline session setup, context management, autonomous workflows, and pre-merge reviews, plus key tips to avoid unexpected costs and boost daily productivity.
That internal usage stat is a useful lens for understanding why the CLI tool's command surface has grown so large. Claude Code exposes 90+ slash commands for controlling session behavior, managing permissions, spawning subagents, reviewing diffs, compacting context, and orchestrating long-running work. Most developers use three or four. The rest sit dormant until you need them.
This guide organizes the command surface by what you're actually trying to accomplish — not alphabetical order. If you've already read our Claude Code commands complete reference, you have the full catalog. Here, I'll focus on the operational patterns and the tradeoffs that matter when you're deciding which commands belong in your daily workflow.
How Commands Fit the Session Lifecycle
Every slash command must appear at the start of a message. Anything after the command name gets passed as arguments.
If you enjoyed this, read the full post at SaaS with Alex
Top comments (0)