agentleFS
greatSuminigreatSumini/cc-system/.claude/skills/slash-command-creator/SKILL.md

slash-command-creator

Skill438 starsChanged 7 months agoMITView on GitHub

Guide for creating Claude Code slash commands. Use when the user wants to create a new slash command, update an existing slash command, or asks about slash command syntax, frontmatter options, or best practices.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create custom slash commands for Claude Code to automate frequently-used prompts.

    line 8
  2. Distinctive:

    Edit: Update description and body

    line 107
  3. Distinctive:

    Test: Run the command in Claude Code

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slash Command Creator

Create custom slash commands for Claude Code to automate frequently-used prompts.

Quick Start

Initialize a new command:

scripts/init_command.py <command-name> [--scope project|personal]

Command Structure

Slash commands are Markdown files with optional YAML frontmatter:

---
description: Brief description shown in /help
---

Your prompt instructions here.

$ARGUMENTS

File Locations

ScopePathShown as
Project.claude/commands/(project)
Personal~/.claude/commands/(user)

Namespacing

Organize commands in subdirectories:

  • .claude/commands/frontend/component.md → /component shows "(project:frontend)"
  • ~/.claude/commands/backend/api.md → /api shows "(user:backend)"

Features

Arguments

All arguments - $ARGUMENTS:

Fix issue #$ARGUMENTS following our coding standards
# /fix-issue 123 → "Fix issue #123 following..."

Positional - $1, $2, etc.:

Review PR #$1 with priority $2
# /review 456 high → "Review PR #456 with priority high"

Bash Execution

Execute shell commands with ! prefix (requires allowed-tools in frontmatter):

---
allowed-tools: Bash(git status:*), Bash(git diff:*)
---

Current status: !`git status`
Changes: !`git diff HEAD`

File References

Include file contents with @ prefix:

Review @src/utils/helpers.js for issues.
Compare @$1 with @$2.

Frontmatter Options

FieldPurposeRequired
descriptionBrief description for /helpYes
allowed-toolsTools the command can useNo
argument-hintExpected arguments hintNo
modelSpecific model to useNo
disable-model-invocationPrevent SlashCommand tool invocationNo

See references/frontmatter.md for detailed reference.

Examples

See references/examples.md for complete examples including:

  • Simple review/explain commands
  • Commands with positional arguments
  • Git workflow commands with bash execution
  • Namespaced commands for frontend/backend

Creation Workflow

  1. Identify the use case: What prompt do you repeat often?
  2. Choose scope: Project (shared) or personal (private)?
  3. Initialize: Run scripts/init_command.py <name>
  4. Edit: Update description and body
  5. Test: Run the command in Claude Code

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.