How to use this cheat sheet
Search for the job you are trying to do, or filter by Claude Code or Codex. Copy the command, then add the details the tool needs when the command accepts an instruction.
This is a curated reference, not a complete command list. Availability can vary by product surface, version, plan, workspace policy, and environment, so check the product help when a command is missing or behaves differently.
Command group
Start and plan
/initCreate the project instruction file the coding assistant should follow.
- Use it when
- Use it the first time you bring an existing project into Claude Code or Codex.
- Example
/init- Documented surfaces
- Claude Code · Codex CLI · Codex IDE
/planAsk for a step-by-step approach before the tool changes anything.
- Use it when
- Use it when the work has several parts, touches important files, or needs a decision before implementation.
- Example
/plan add account deletion without changing the billing flow- Documented surfaces
- Claude Code · Codex app · Codex CLI · Codex IDE
/goalSet a concrete outcome for longer-running work.
- Use it when
- Use it when you want the agent to keep the finish line visible across several steps.
- Example
/goal design, build, and verify a complete working website; preserve the existing content, run all tests, and finish with a successful production build- Documented surfaces
- Claude Code · Codex app · Codex CLI · Codex IDE
Command group
Manage context
/compactCondense a long session so the important context remains easier to work with.
- Use it when
- Use it when the conversation is getting long or the tool warns that context is running low.
- Example
/compact keep the final API decisions and unresolved test failures- Documented surfaces
- Claude Code · Codex CLI · Codex IDE
/contextSee what is using the current context window.
- Use it when
- Use it when Claude Code feels crowded and you want to understand what is taking up space.
- Example
/context- Documented surfaces
- Claude Code
/statusShow the current session, model, account, and environment details available on that surface.
- Use it when
- Use it when you need to confirm what model or workspace the session is actually using.
- Example
/status- Documented surfaces
- Claude Code · Codex CLI · Codex IDE
Command group
Steer the session
/modelView or change the model used for the current work.
- Use it when
- Use it when you want a faster model for a small task or a stronger model for harder reasoning.
- Example
/model- Documented surfaces
- Claude Code · Codex app · Codex CLI · Codex IDE
/permissionsReview or change what the assistant can do without asking first.
- Use it when
- Use it before sensitive work or when approval prompts are either too loose or too restrictive.
- Example
/permissions- Documented surfaces
- Claude Code · Codex CLI
/mentionAdd a file to the conversation by typing part of its path.
- Use it when
- Use it when Codex needs a specific file and you do not want to paste its contents.
- Example
/mention app/api/contact/route.ts- Documented surfaces
- Codex CLI
/skillsBrowse the reusable skills available in the current environment.
- Use it when
- Use it when a repeatable workflow may already have instructions or tools ready to use.
- Example
/skills- Documented surfaces
- Claude Code · Codex CLI
Command group
Review and continue
/diffShow the changes made in the working project.
- Use it when
- Use it before accepting, committing, or handing off code changes.
- Example
/diff- Documented surfaces
- Claude Code · Codex CLI
/reviewAsk the tool to inspect code changes for defects and risks.
- Use it when
- Use it after implementation and before you merge or deploy.
- Example
/review focus on authentication and data-loss risks- Documented surfaces
- Claude Code · Codex CLI · Codex IDE
/resumeReopen a previous coding session and continue from its saved context.
- Use it when
- Use it when you return to unfinished work instead of rebuilding the conversation from memory.
- Example
/resume- Documented surfaces
- Claude Code · Codex CLI