Skip to content
Mia Automation
NLEN Sign in Put Mia to workGet started

Claude Code Commands: The Cheat Sheet We Use Every Day

Claude Code has more than 60 slash commands, but about a dozen cover a normal working day: /init, /plan, /context, /compact, /clear, /resume, /rewind, /diff and /code-review among them. Below is a one-page cheat sheet with those, the start-up flags and the keys we use. We checked the flags in the help output of Claude Code 2.1.322 on Windows, ran a custom command on 2.1.321 on Linux, and took the slash commands and keys from Anthropic's reference on November 11, 2026.

Claude in practiceUpdated 7 min read

Tested by us on 11 November 2026.

Claude Code cheat sheet with three columns: everyday slash commands like /init, /plan, /compact and /code-review; start-up flags like claude -c and -p; keys like Esc, Shift+Tab and Ctrl+O; and a row of removed or renamed commands (opens at full size)
Right-click to save or print. Checked November 11, 2026.

The commands to learn first

Type / in a session to see every command; a few letters filter the list. The table is ranked by how often each one saved us time. Learn the first three in your first week and the rest when you hit the situation in the third column.

#CommandWhen it pays offSkip it when
1/initFirst session in a repo: writes a starter CLAUDE.md you then trimThe repo already has a CLAUDE.md you trust
2/planChanges that touch more than a few files; you approve the plan before any editA one-file fix: the plan costs a round trip
3/contextAnswers get vague; it shows what fills the windowThe session is young
4/compactLong session, same task. In our test it cut 75.2k tokens to 33.8kYou're switching tasks: use /clear
5/clearNew task. Starts empty, project memory staysYou still need the earlier details
6/rewindClaude went the wrong way: roll back its edits and the chatThe damage came from shell commands; use Git
7/diff + /code-reviewBefore you commit; --fix applies the findingsThrowaway experiments
8/usageClose to your plan limitPay-as-you-go API keys with their own dashboard
Animated diagram of one session in six steps lighting up in turn: /init for a new repo, /plan for a big change, Esc to steer, /compact when the chat gets long, /code-review before shipping, /clear for the next task

What /context and /compact did in our test

We asked Claude Code 2.1.321 to read three Python files and summarize them, then ran /context in the same session. It reported 75.2k tokens in use, 60.3k of them conversation, the rest system prompt, tools and skill descriptions. After /compact the same session showed 33.8k, with the conversation down to 18.9k. The summary kept the task and the three file names. The full file contents were gone, so Claude would have to read them again for details.

That's the trade-off. Compact when the old details are done with, and give it a focus such as /compact keep the test output when something must survive. Use /clear when the next task has nothing to do with the last one.

Start-up flags worth knowing

Flags go after claude when you start it. We checked each of these in claude --help on version 2.1.322 on a Windows PC.

FlagWhat it does
claude -cContinue the most recent conversation in this folder
claude -rPick a conversation to resume, or pass its ID or name
claude -p "prompt"Run one prompt, print the answer and exit; the basis for scripts
--permission-mode planStart in plan mode. Other choices: acceptEdits, auto, manual, dontAsk, bypassPermissions
--model sonnetPick the model for this session
--add-dir ../sharedLet Claude read and edit a second folder
--output-format jsonWith -p: structured output you can parse
PowerShell window on Windows 10 showing claude --version 2.1.322 and the help lines for --add-dir, --continue, --model, --permission-mode, --print and --resume (opens at full size)
Run claude --help yourself after an update; it always matches the version you have.

Keys and prefixes

What we verified ourselves: the flags (help output on 2.1.322), claude -p and a custom command (2.1.321). The slash commands and keys come from Anthropic's reference; shortcuts can differ per terminal, especially Option and Alt combinations on a Mac.

  • Esc stops Claude mid-turn and keeps the work so far, so you can redirect. Esc Esc on an empty prompt opens the rewind menu.
  • Shift+Tab cycles permission modes: manual, accept edits and plan. Bypass and auto mode join the cycle only when your settings and plan allow them.
  • Ctrl+O shows the full transcript with every tool call. Use it when you want to know what Claude ran.
  • Ctrl+R searches earlier prompts. Ctrl+B sends a running command or agent to the background.
  • An exclamation mark at the start runs a shell command yourself and adds its output to the conversation, for example before git status. @ mentions a file.

What we left off the sheet, and why

These are useful, but only in specific setups. The commands /background and /batch are for running several agents at once on a large codebase. With /remote-control and /teleport you move a session between your machine, the browser and your phone. Scheduled cloud tasks live under /schedule. And /mcp, /hooks and /permissions are setup screens you open once per project, not every day.

We also left out aliases. The alias /new does the same as /clear, and /undo the same as /rewind. One name per action is easier to remember; the menu shows the alias when you type it.

Make your own slash command

A custom command is a Markdown file. Put it in .claude/commands/ for one project or ~/.claude/commands/ for all of them; the file name becomes the command. Claude Code has merged commands into skills, so .claude/skills/standup/SKILL.md gives you the same /standup, with room for extra files. This is the one we tested:

markdown
---
description: Short Monday standup from the last 7 days of commits
---
Read `git log --since="7 days ago" --oneline` and write for Monday's standup:
1. What got done (one line per commit, in plain English).
2. What stands out or is still open.
Eight lines max, no intro.

.claude/commands/standup.md

In a test repo with three commits, claude -p "/standup" answered in 5.6 seconds. It listed the three changes in plain English and then flagged two things we hadn't asked about: the .claude/ folder wasn't committed, and the work sat on master while the repo's main branch was main. That second part is the reason to keep "what stands out" in the prompt.

Removed and renamed

From Anthropic's command reference, checked November 11, 2026.
OldWhat to do now
/vimRemoved in 2.1.92. Switch the editor mode in /config
/pr-commentsRemoved in 2.1.91. Ask Claude to read the PR comments
/ultraplanRemoved. Start in plan mode instead
/reviewKeep using it if you like: it's now an alias of /code-review
/cost, /statsSame screen as /usage; learn that one
/bug, /shareSince 2.1.212 their own bug report command, no longer aliases of /feedback

Questions

Which Claude Code commands should I learn first?

/init, /plan and /context, then /compact, /clear and /rewind. Together they decide how a session starts, how big changes get planned and how you recover when things drift.

How do I see all slash commands?

Type / in a session. The full list with descriptions is in Anthropic's commands reference; it changes with most releases.

How do I make my own slash command?

Create .claude/commands/name.md in your project with the instructions in Markdown, or a skill folder with SKILL.md. Then type /name.

Can I use slash commands with claude -p?

Yes for commands and skills that produce text, like our /standup. Commands that open a dialog only work in an interactive session.

Sources