slash-command-builder

Create custom slash commands for Claude Code with syntax, arguments, bash execution, file references, and frontmatter configuration.

37|4|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill slash-command-builder-mike-coulbourn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slash-command-builder
Source: https://github.com/mike-coulbourn/claude-vibes/tree/main/plugins/vibes/skills/slash-command-builder
Command: npx skills add https://github.com/mike-coulbourn/claude-vibes --skill slash-command-builder-mike-coulbourn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the creation of custom slash commands for Claude Code, enabling users to automate repetitive tasks and integrate external tools directly into their AI workflow. It provides a structured approach to command design, ensuring they are discoverable, robust, and follow best practices.

Core Features & Use Cases

  • Guided Command Creation: Follow a step-by-step workflow from defining purpose to testing for effective command development.
  • Argument Handling: Learn to design commands that accept and process user arguments, making them flexible and powerful.
  • Tool Integration: Understand how to leverage various tools (e.g., Bash, Read, Write) within your commands to interact with the environment.
  • Use Case: You frequently need to check the status of your Git repository. This skill helps you create a /git-status command that runs git status and presents the output clearly, saving you keystrokes and ensuring consistent execution.

Quick Start

Ask the slash-command-builder to help you create a new command to check the current Git branch.

Frequently Asked Questions about slash-command-builder

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 let you automate repetitive tasks in Claude Code by defining command syntax, arguments, and bash execution logic. Start by specifying your command's purpose, design argument handling with $ARGUMENTS or $1/$2 syntax, configure frontmatter restrictions, and test the command end-to-end before deploying it across your workflows.

Can I use file references and arguments in my slash commands?

Yes. Slash commands support dynamic file references using @paths and flexible argument handling through $ARGUMENTS and positional parameters like $1 and $2. This lets you build commands that accept user input and operate on specific files, making them adaptable to different workflows and project structures.

What's the best way to integrate external tools into Claude Code?

Slash commands integrate external tools by leveraging bash execution and Claude Code's built-in components like Read and Write. Define your tool's execution logic in the command template, map user arguments to tool inputs, and use frontmatter configuration to control scope and validation, enabling seamless tool integration into your AI workflow.

Do I need to learn bash scripting to build slash commands?

No. The slash-command-builder guides you through structured command design without requiring advanced bash expertise. You follow a step-by-step workflow to define purpose, configure arguments, set up file references, and validate behavior, making command creation accessible even if you're new to bash or automation.

How do slash commands improve workflow consistency?

Slash commands standardize repetitive tasks by encoding best practices into reusable templates. Once created, commands execute consistently with proper argument handling and tool integration, eliminating manual variations and reducing keystrokes while ensuring reliable output across personal and project-level use cases.

What happens if my slash command arguments don't validate correctly?

Frontmatter configuration in slash commands enables validation rules that check argument format and constraints before execution. If validation fails, the command stops and returns feedback, preventing incorrect bash execution and ensuring only well-formed inputs reach your tools and file operations.