Create Cmd Args

The user wants to take their previous message — the most recent user turn in this conversation before this invocation — and save it as a reusable custom slash command that is parameterized, so the variable parts become arguments.

Raw arguments: $ARGUMENTS

Do this:

1. Parse $ARGUMENTS into a name and an optional scope flag:

• --global / -g / global -> system-wide.
• --project / -p / project -> current project.
• Everything else is the command name.

1. If no name is given, STOP and ask for one. A name is required.
2. Determine where to save (scope):

• If a scope flag was given, use it.
• Otherwise ASK with AskUserQuestion: "Where should / be saved?" -> Global or

Project.

• Global path: ~/.claude/commands/
• Project path: /.claude/commands/ — create if missing; fall back

to Global if not in a project and say so.

1. Normalize the name: lowercase, kebab-case, strip any leading / and .md.
2. Find the user's previous prompt (the message right before this call).
3. Identify the parts of the prompt that are specific values likely to change each run — a

filename, a topic, a function/variable name, a language, a count, etc. Replace them with placeholders:

• One variable -> $ARGUMENTS.
• Multiple variables -> $1, $2, $3 in the order they should be passed.

Keep the fixed instructions intact.

1. Add YAML frontmatter with a one-line description and an argument-hint listing the

placeholders in order, e.g. argument-hint: .

1. Show the user the parameterized prompt and how to call it (e.g. / utils.js python).
2. Write the file to /.md.
3. If that file already exists, show its current contents and ask before overwriting.
4. Confirm: print the saved file path, the scope, and that / is now available.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: fayis672
• Source: fayis672/slash-IT
• License: MIT

Install and usage instructions live in the source repository linked above.