20 Claude Code Commands Every Developer Should Know

A recent Reddit post on r/ClaudeAI (by user irelatetolevin) compiles 20 Claude Code commands that solve real workflow problems. Here's the breakdown by category.
Stopping, Undoing, Branching
- Esc stops the current task without losing conversation history — only the in-flight action dies.
- Double-tap Esc or
/rewindopens a menu to restore code and conversation, restore conversation only, restore code only, summarize from here, or cancel. /btwasks a side question without polluting the main thread — e.g.,/btw where is the test file again. It reuses the existing prompt cache, so token cost is near zero./branchforks the conversation, letting you run two approaches in parallel and keep the one that works.
Managing the Context Window
/compactrewrites long history into a summary that keeps the storyline, technical decisions, and errors plus fixes. Prevents context window bloat./clearwipes everything for a fresh topic./exportsaves the conversation as Markdown to~/projects/XXX/claude-session-YYYY-MM-DD-HH-MM.md— useful after an hour of architecture design./resumesearches old sessions by keyword.claude -cpicks up yesterday's chat where you left off.claude -rlists every past session and lets you jump back into a specific one./remote-control(alias/rc) hands the running session over to your phone — work keeps executing on your machine, you steer from elsewhere.
Working Smarter
/model opusplanruns Opus for planning and Sonnet for execution: slower thinking on design, faster code output./simplifyspins up three parallel reviewers (architecture/code reuse, code quality, efficiency) and returns one combined report./insightsgenerates a local HTML report at~/.claude/usage-data/report.htmlshowing usage habits, common mistakes, features never touched, and suggestions for your CLAUDE.md./loopschedules recurring or one-shot tasks inside the session — e.g.,/loop 15m check the deploy. Recurring loops auto-expire after 3–7 days to avoid burning API budget. Override defaults with a.claude/loop.mdfile — bare/loopruns the instructions inside.
Keyboard Shortcuts
- Ctrl+V pastes screenshots directly — no saving to disk first.
- Ctrl+J (or Option+Enter on Mac) inserts a newline without sending, enabling multi-line prompts safely.
- Ctrl+R searches your prompt history — your own personal prompt library.
- Ctrl+U clears the entire input line in one keystroke.
/skills [name]loads project-specific skills. Run/skillswith no argument to see what's available in the current workspace.
These commands are immediately actionable — especially /compact, /branch, and /remote-control for managing complex sessions.
📖 Read the full source: r/ClaudeAI
👀 See Also

Worker Agents Shouldn't Write Memory Directly: A Curator-Agent Pattern
A Reddit post details a Memory Curator pattern that prevents worker agents from writing directly to shared memory, routing events through a validation and scoping layer.

Most People Use Claude at 5% of Its Capacity – Here's How to Fix It
After 60+ hours testing prompts on Claude Opus 4.7, a user shares a 5-step recipe: assign role, load specific context, set constraints, define output format, add forcing function.

Day 1 Configuration: Prevent 90% of Common OpenClaw Problems
Set spending limits, write a SOUL.md, and adjust heartbeat interval to avoid surprise bills, rogue behavior, and cost shock.

How I Prompt AI Models in 2026 vs a Year Ago: 3 Key Changes
A developer shares three concrete changes: switch from prompt templates to reusable skills, write goals instead of step-by-step instructions, and use /loop commands for long-running projects in Claude Code and Codex.