Custom slash commands

Custom slash commands let you bind a frequently-used prompt template to a short trigger like /standup or /review-pr.

File location

~/.lime/commands/<name>.md

The filename (without .md) becomes the trigger. Custom commands are user-scoped only — they live in your home directory, not in the project.

For project-scoped equivalents, use a plugin.

File format

Plain Markdown with optional YAML frontmatter:

---
description: Summarize a PR for the team channel
argument-hint: [pr-number]
---

Read the PR description and diff for PR #{ARG1}, then write a 3-bullet
summary suitable for the team Slack channel.

Focus on:
- What the change does
- The biggest risk reviewers should look at
- Whether tests cover the change

Frontmatter keys:

• description — surfaced in the slash palette.
• argument-hint — short hint shown after the trigger.

Placeholders

Placeholder	Replaced with
{ARGS}	The full argument string after the trigger.
{ARG1}, {ARG2}, …	Positional tokens, splitting on whitespace.

If the template contains no placeholder and the user supplies arguments, the arguments are appended as a new paragraph.

Manage from the CLI

lime command list
lime command show <name>
lime command create <name>
lime command edit <name>
lime command delete <name>

lime command create <name> opens your $EDITOR on a new template file; lime command edit <name> opens an existing one. Both paths normalize the filename and frontmatter for you.

/command, /cmd, /commands are the slash-command equivalents inside the REPL.

How they appear in the palette

Custom commands surface alongside built-ins in the /-palette, sorted by fuzzy-match score. Built-ins shadow collisions: a custom ~/.lime/commands/init.md is hidden because /init is a built-in.

Examples

A standup template:

---
description: Daily standup writeup from the last 24h of git activity
---

Summarize the last 24 hours of activity in this repo for a daily standup.
- Group by author.
- Highlight any PRs merged or opened.
- Mention any failing CI runs.

A bug-triage template that takes a positional arg:

---
description: Triage a GitHub issue
argument-hint: <issue-number>
---

Pull GitHub issue #{ARG1}. Read the report, look for related issues,
and produce:
- A 2-sentence summary.
- A guess at root cause with file/line pointers.
- A suggested labelling.