Claude Code Slash Commands Before Friday’s Release

It is Thursday afternoon, a release is due Friday, and you have opened Claude Code in an unfamiliar repository. You could spend the next hour repeating project instructions, untangling a long conversation and approving the same routine actions. A few slash commands can reduce that overhead.

A slash command is an instruction to Claude Code itself, rather than a request for it to write or explain code. Type a forward slash in the interactive prompt to see available commands. Availability can vary by version, authentication method and environment, so treat your installed command menu as the final reference.

/help: Find the Controls Without Leaving the Terminal

Start with /help. It shows the commands and help available in your installation. This is faster than copying a command from an old tutorial and wondering why it does not work.

You do not need to memorize the whole menu. Learn the commands that remove repeated work: project instructions, conversation cleanup, session recovery and permission management.

/init: Stop Repeating the Repository Basics

Run /init when you first work in a repository. It helps create a CLAUDE.md file containing instructions Claude Code can use in future sessions. If the repository already has one, inspect it before asking for changes.

The time savings come from recording facts you would otherwise repeat:

• The exact command for running the relevant tests.
• The package manager the team uses.
• Directories containing generated files that should not be edited.
• Local conventions, such as where API handlers and fixtures belong.

Review the result. A guessed test command is not useful documentation, and credentials do not belong in project instructions. Keep the file short enough that important rules remain easy to spot.

/context and /compact: Keep a Long Debugging Session Useful

Claude Code has a limited working context: the material it can consider during a conversation. File reads, tool output and repeated debugging attempts all occupy that space. Run /context to inspect context usage rather than guessing whether the session is getting crowded.

Use /compact when the task is still the same but the conversation has accumulated too much history. It summarizes the conversation so you can continue with less material in context. You can provide a focus, for example: /compact Preserve the failing test, files changed, and remaining checks.

Before compacting, make sure important decisions are recorded somewhere durable. A summary is not a perfect transcript. For a release fix, a short note naming the bug, chosen approach and verification command is often enough to prevent repeated investigation.

/clear and /resume: Separate Tasks Without Losing Your Place

Use /clear when moving to an unrelated task. Yesterday's authentication investigation should not shape today's CSS fix. Clearing the conversation gives the new task a clean context; it does not undo file changes.

Use /resume to return to an earlier conversation instead of reconstructing its background from memory. This is particularly useful after an interruption or when switching between two pieces of work.

The distinction is simple: compact to continue the same job, clear to start a different one, and resume to reopen previous work. Always check the repository state before continuing, because files may have changed since that conversation.

/permissions: Remove Friction Without Removing Guardrails

If repeated approval prompts interrupt routine work, inspect /permissions. Review the rules and keep any allowances narrow and understandable.

Check what a command actually does before allowing it. A test script can invoke other scripts, access services or modify files. Broad approval may feel faster, but it can turn a small misunderstanding into a larger cleanup job. Preserve review for destructive operations, credential access and deployment actions.

A Small Command Routine for Release Work

For your next task, check /help, review project instructions, and watch context usage during long investigations. Add the other commands when a real interruption makes them useful.

If you want pay-as-you-go model access for this workflow, RelayVano works with Claude Code and offers a practical option for developers across countries. Sign up for RelayVano when you are ready to connect your setup; check its current configuration instructions rather than assuming endpoint and authentication settings are interchangeable across tools.