12 Slash Commands That Save Hours Per Week

Custom slash commands are Claude Code's secret weapon. These 12 examples show what's possible when you stop typing the same prompts over and over.

If you're typing the same prompt more than twice, it should be a slash command. Here are 12 that real teams are using to save hours every week.

1. /review

Runs a code review on staged changes. Checks for security issues, performance problems, and style violations. One command replaces a 15-minute manual review.

2. /test

Generates tests for the current file. Reads the code, infers edge cases, writes tests. You review instead of writing from scratch.

3. /deploy

Runs your full deploy pipeline — build, test, lint, push. One command. No forgetting steps.

4. /morning

Reads your latest handoff, checks git status, shows open PRs and failing CI. Your entire daily standup context in 10 seconds.

5. /refactor

Analyzes a file for code smells and suggests improvements. Accept them one by one or all at once. Refactoring without the mental overhead.

6. /ticket

Creates a Jira/Linear ticket from a description. Formats it properly, adds acceptance criteria, and even suggests labels. PMs love this one.

7. /explain

Explains a complex function or file in plain English. Perfect for onboarding or revisiting code you wrote 6 months ago and no longer understand.

8. /migrate

Applies a migration pattern across matching files. "Convert all class components to functional" or "replace axios with fetch." Batch operations made safe.

9. /handoff

Writes a structured handoff document capturing what you did, what's left, and any blockers. Future-you will be grateful.

10. /pr

Creates a pull request with auto-generated title, description, and test plan from your commits. The PR description problem, solved.

11. /debug

Reads the error, checks recent changes, suggests fixes. Cuts the "stare at the stack trace" phase from 20 minutes to 2.

12. /cleanup

Finds dead code, unused imports, and orphaned files. Keeps your repo lean without the fear of accidentally deleting something important.

Building these is trivial — just markdown files in .claude/commands/. The slash commands guide shows you exactly how.