In this categoryClaude Code ยท 45
- How to Install Claude Code on macOSStart
- How to Install Claude Code on Windows Natively (No WSL)
- How to Install Claude Code on Windows with WSL
- How to Start Your First Project with Claude Code
- How to Create a CLAUDE.md File for Your Project
- How to Configure Claude Code with settings.json
- How to Layer Global, Project, and Local CLAUDE.md Files
- How to Set Up a Permissions Allowlist in Claude Code
- How to Use Claude Code Inside VS Code
- How to Add a Custom Slash Command in Claude Code
- How to Create a Custom Slash Command in Claude Code
- How to Pass Arguments to a Claude Code Slash Command
- How to Use Claude Code Slash Commands (Full List + Examples)
- How to Add Custom Slash Commands to Claude Code (Arguments + Frontmatter)
- How to Fix command not found After Installing Claude Code
- How to Add Any MCP Server to Claude Code
- How to Connect an MCP Server to Claude Code
- Best MCP Servers for Coding in 2026
- How to Add a Filesystem MCP Server to Claude Code
- How to Connect the GitHub MCP Server to Claude Code
- How to Create Your First Subagent in Claude Code
- Context7 Alternatives: MCP Servers for Up-to-Date Docs
- How to Manage MCP Server Scopes in Claude Code
- How to Restrict the Tools a Subagent Can Use
- How to Debug a Failing MCP Server in Claude Code
- How to Generate Unit Tests for a Function with Claude Code
- How to Refactor a Long Function Safely with Claude Code
- How to Debug a Failing Test with Claude Code
- How to Review Your Own Diff Before Committing with Claude Code
- How to Rename a Symbol Across the Codebase with Claude Code
- How to Review a Teammate's Pull Request with Claude Code
- How to Raise Test Coverage on a Specific File with Claude Code
- How to Debug a Runtime Error from a Stack Trace with Claude Code
- How to Add an Integration Test for an API Route with Claude Code
- How to Teach Claude Code Your Test Conventions with CLAUDE.md
- How to Find Which Commit Broke a Test with Claude Code
- How to Set Up Hooks for Automation in Claude Code
- Claude Code Hooks Explained: Events, Config, and Blocking
- How to Block Risky Commands with a Claude Code Hook
- How to Auto-Format Files After Edits with a PostToolUse Hook
- How to Get a Notification When Claude Code Finishes a Task
- How to Give a Coding Agent a Clear Stop Condition
- How to Make an Agent Plan Before It Edits
- How to Keep an Agent Session Focused by Clearing Context
- How to Pin a Specific Model for One Project
How to Add a Custom Slash Command in Claude Code
Save a reusable prompt as a Markdown file so a single slash command runs your repeatable workflow on demand.
If you find yourself typing the same long instruction again and again, turn it into a custom slash command. Claude Code reads command definitions from Markdown files, so /review or /changelog can run a saved prompt in one keystroke. This guide creates one and parameterizes it.
What you need
- Claude Code installed in a project
- A prompt or workflow you repeat often
- About 8 minutes
Step 1: Create the commands folder
Project commands live in .claude/commands. Each Markdown file becomes a command named after the file. Create the folder.
Step 2: Write the command file
Put your prompt in a file. The body is sent to the agent when you invoke the command. Save this as review.md to create /review.
Review the staged changes for bugs, missing tests, and style issues.
Group findings by severity. Suggest a concrete fix for each.
Do not change any files; only report.Step 3: Accept arguments
Use the $ARGUMENTS placeholder to pass input. Anything typed after the command name is substituted in. This file makes /changelog accept a version tag.
Write a CHANGELOG entry for version $ARGUMENTS.
Summarize merged changes since the last tag under
Added, Changed, and Fixed headings. Keep it terse.Step 4: Run it
Inside a session, type the slash and the command name. Pass arguments after it where defined.
Result: your repeatable workflows are one slash away, consistent every time, and shareable with anyone who clones the repo.
Watch related tutorials
16:30
19:27
1:42:18
28:14
41:09
9:47New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.