Create cmd instruct
A Claude Code plugin. Turn any message you just typed into a reusable slash command
npx -y skills add fayis672/slash-IT --skill create-cmd-instructAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Reshape my PREVIOUS message using extra instructions, then save it as a slash command
SKILL.md
2.5 KB, as published. Nobody here has run it
The user wants to take their previous message — the most recent user turn in this conversation before this invocation — modify it according to extra instructions they provide here, and save the result as a reusable custom slash command.
Raw arguments: $ARGUMENTS
The arguments contain a command name and instructions for how to change the prompt,
separated by a | pipe. An optional scope flag may appear in the name part. Example:
/slash-it:create-cmd-instruct daily-report --project | output a markdown table and ask for the date
Do this:
- Split
$ARGUMENTSon the first|.- Left side = the command name (and optional scope flag).
- Right side = the user's instructions for reshaping the prompt.
If there is no
|, treat the first token as the name and the rest as instructions.
- From the left side, extract the name and any scope flag:
--global/-g/global-> system-wide.--project/-p/project-> this project.
- If the name is empty, STOP and ask for it (required). If the instructions are empty, ask what changes the user wants.
- Determine where to save (scope):
- If a scope flag was given, use it.
- Otherwise ASK with AskUserQuestion: "Where should
/<name>be saved?" -> Global or Project. - Global path:
~/.claude/commands/ - Project path:
<current working directory>/.claude/commands/— create if missing; fall back to Global if not in a project and say so.
- Normalize the name: lowercase, kebab-case, strip any leading
/and.md. - Find the user's previous prompt (the message right before this call).
- Produce a new prompt = the previous prompt transformed according to the instructions, plus
light optimisation (clarity, structure, grammar) while honoring the original intent. Parameterize
with
$ARGUMENTS/$1/$2where it makes the command reusable. - Briefly show the user the resulting prompt so they can see what was saved.
- Add YAML frontmatter with a one-line
descriptionand anargument-hintif parameters exist. - Write the file to
<chosen path>/<name>.md. - If that file already exists, show its current contents and ask before overwriting.
- Confirm: print the saved file path, the scope, and that
/<name>is now available.