/helpCoreShow available commands and shortcuts.
Use it when you forget a command or want to discover project commands.
/helpFree Tool
Free Claude Code Commands Cheat Sheet
A Claude Code commands cheat sheet is a searchable reference for the CLI commands, slash commands, and prompt shortcuts you use while coding with Claude Code. Search by task, filter by workflow, and copy the exact example you need.
/initWorkflowCreate or refresh the project memory file.
Run it at the start of a new repo so Claude understands conventions.
/init/clearCoreClear the current conversation context.
Use it before switching tasks or after a long thread gets noisy.
/clear/compactContextSummarize the current session to save context.
Use it before context gets full but you still want the task history.
/compact Keep the current bug, files touched, and failed tests./costCoreInspect session usage and estimated spend.
Use it during long runs to see how much the current work costs.
/cost/modelCoreSwitch the model used for the session.
Use it when a task needs a faster or stronger model profile.
/model/permissionsTerminalReview or change tool permission behavior.
Use it when a command is blocked or you want a stricter session.
/permissions/terminal-setupTerminalInstall terminal integration helpers.
Use it when shell shortcuts or terminal handoff are not working.
/terminal-setup/reviewWorkflowAsk Claude to review the current changes.
Use it before committing when you want bug-focused feedback.
/review/pr-commentsWorkflowWork through pull request comments.
Use it when a PR has review feedback that needs triage or fixes.
/pr-comments/vimTerminalToggle vim keybindings.
Use it if you prefer modal editing inside Claude Code.
/vim/memoryContextEdit or inspect Claude Code memory.
Use it when persistent instructions are stale or missing.
/memory/agentsWorkflowList or manage subagents.
Use it when you want a specialized role for repeated workflows.
/agents/mcpTerminalInspect connected MCP servers and tools.
Use it when a tool server is missing, stale, or not authenticating.
/mcp!TerminalRun a shell command from the prompt.
Use it for quick terminal checks without leaving Claude Code.
!git status --short@ContextReference a file or folder in the prompt.
Use it to pin exact code context before asking for a change.
@src/app/page.tsx Explain this file.How to use this Claude Code command list
- Search for the task. Type the workflow you are trying to run, such as review, memory, MCP, or terminal, into the search box.
- Filter by command type. Use the Core, Workflow, Context, and Terminal filters to narrow the command list.
- Read when to use it. Check the short explanation to confirm the command fits the current job.
- Copy the example. Copy the example command and adjust the file path, prompt text, or arguments for your project.
Fast rules for choosing a command
Use /init for project memory
Run it when a repo has no Claude instructions or when the existing memory is stale.
Use @ for exact file context
Reference the file before asking for an explanation, bug fix, or targeted refactor.
Use ! for quick shell checks
Run small read-only commands like git status, test listings, or package scripts.
Use /compact before context gets full
Preserve the useful task state without dragging every old message forward.
Frequently Asked Questions
What is the Claude Code commands cheat sheet?
+
The Claude Code commands cheat sheet is a searchable reference for common Claude Code slash commands, terminal helpers, context shortcuts, and workflow commands. It explains what each command does, when to use it, and gives a copyable example.
What is the difference between slash commands and shortcuts?
+
Slash commands start with / and run Claude Code workflows such as help, review, compact, or project commands. Shortcuts such as @file and !command are prompt helpers for adding file context or running shell commands.
Which Claude Code command should I run first in a new repo?
+
Run /init first in a new repo. It helps create or refresh the project memory file so Claude Code can follow the repository's commands, architecture, testing rules, and coding conventions.
When should I use /compact instead of /clear?
+
Use /compact when you want to keep a summary of the current task while reducing context. Use /clear when you want a clean conversation and do not need the previous session details.
Can I create my own Claude Code commands?
+
Yes. Claude Code supports custom slash commands stored as Markdown files. Project commands usually live in .claude/commands, while user commands usually live in your home Claude commands folder.
Commands help. Repeatable workflows help more.
Claude Code commands are useful shortcuts. Tornic turns recurring CLI work into deterministic multi-step automations that run the same way every time across Claude, Codex, and Cursor.
Try Tornic