slash-commands

Create Claude Code slash-command definitions with YAML frontmatter and Markdown bodies.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/putto11262002/jimmodel --skill slash-commands-putto11262002
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slash-commands
Source: https://github.com/putto11262002/jimmodel/tree/main/.claude/skills/slash-command-creator
Command: npx skills add https://github.com/putto11262002/jimmodel --skill slash-commands-putto11262002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Repetitive tasks and complex prompts can slow down development. This skill empowers users to create custom slash commands for Claude Code, transforming common workflows into single, reusable commands with tailored prompts, tool access, and argument handling, significantly boosting productivity.

Core Features & Use Cases

  • Custom Command Definition: Define commands with YAML frontmatter for metadata and Markdown for the prompt body.
  • Tool Integration: Restrict or grant access to built-in tools (Bash, Edit, View) and MCP tools for precise control.
  • Argument Handling: Use $1, $2, $ARGUMENTS placeholders for dynamic command execution.
  • Use Case: Create a /code-review <filepath> command that automatically views the specified file, applies a detailed code quality checklist, and suggests improvements, saving time on manual reviews.

Quick Start

Create a new slash command called 'code-review' that takes a filepath as an argument and reviews it for common issues.

Frequently Asked Questions about slash-commands

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create custom slash commands for Claude Code?

Custom slash commands are reusable prompts defined with YAML frontmatter and Markdown body. Create a command file in `.claude/commands` (project-level) or `~/.claude/commands` (user-level) with metadata, prompt content, and argument placeholders like `$1` or `$ARGUMENTS` to automate repetitive workflows.

Can I control which tools my slash commands can access?

Yes, tool access is controlled via the command's YAML frontmatter. You can restrict or grant access to built-in tools (Bash, Edit, View) and MCP tools, letting you define precise permissions for each custom command.

What template types are available for building slash commands?

The skill provides templates for basic commands, file-analysis, multi-arg, and git-workflow use cases. Each template includes pre-structured YAML and Markdown sections tailored to different command patterns and argument handling needs.

How do I pass arguments to my custom slash commands?

Use placeholders in your command's Markdown body: `$1` for the first argument, `$2` for the second, or `$ARGUMENTS` to capture all arguments dynamically. These are substituted when the command runs.

Can I use custom slash commands at both project and user scope?

Yes, slash commands work at both project-level (`.claude/commands`) and user-level (`~/.claude/commands`). Project-level commands override user-level ones with the same name, enabling both global workflows and project-specific customization.

What happens if I create a slash command with a name that already exists?

The skill includes overwrite safeguards to prevent accidental replacement. New commands at the same scope level follow confirmation or naming conventions to ensure existing commands aren't silently replaced.