Guide

Claude Code slash commands: the ones that actually matter

Claude Code slash commands: the ones that actually matter

Every Claude Code release adds commands, and /help will always be the authoritative list for the version you're running. This is the other thing you need: the shortlist that deserves muscle memory, grouped by what it does for you — with the honest note on where each one stops.

Session hygiene: /compact, /clear, /resume

Setup and control: /model, /init, /permissions, /mcp

Doing the work: /review, /background, /tasks, /agents

The meta set: /help, /status, /cost, /doctor

/help is the real index. /status shows account, model, and where you stand against limits before the lockout surprises you. /cost keeps API spending visible per session. /doctor diagnoses a broken install before you reinstall anything.

Write your own: custom commands

The underrated feature hiding in plain sight: any Markdown file in .claude/commands/ becomes a slash command — filename is the command, body is the prompt, $ARGUMENTS takes what you type after it.

# .claude/commands/write-tests.md
Write unit tests for $ARGUMENTS. Match the existing test style,
cover the edge cases, and run the suite to confirm green.

Commit the folder and the whole team gets the same /write-tests. Repeated prompts are process; process belongs in the repo.

Frequently asked questions

How do I see all slash commands?

Type /help in a session — it lists everything your version supports, including custom commands. The set changes with releases; /help is always current.

What does /compact do and when should I run it?

Summarizes the session and continues compressed. Run at checkpoints — after a subtask, before a new area. It keeps context sharp and is the cheapest way to stretch usage limits.

Can I create my own slash commands?

Yes — Markdown files in .claude/commands/ (project) or ~/.claude/commands/ (user); $ARGUMENTS interpolates your input. Commit the project folder to share with the team.

Is there a command to run Claude Code in the background?

Yes — /background (/bg) detaches the session; /tasks lists background work. Getting notified when the detached agent needs you is the part commands don't cover — that's hooks, or an overlay.

Where Backgrind fits

Slash commands run the session; Backgrind runs the day. It wraps your real claude CLI in an always-on-top overlay — every command above works untouched — and adds the layer commands can't: ambient pings when any session needs a decision, inline approve from the toast, tabs for multiple agents, and your phone as the answer button when the chime catches you in the kitchen. Type /bg; let the overlay handle the part after.