Qwen Code custom commands: .qwen/commands Markdown files, {{args}}, !{shell} and @{file}

• User commands: ~/.qwen/commands/, available in every project.
• Project commands: .qwen/commands/ in the project root. Commit them so your team gets the same commands.
• If a project command and a user command have the same name, the project command wins.
• Subfolders become namespaces with a colon: ~/.qwen/commands/test.md is /test and .qwen/commands/git/commit.md is /git:commit.

A command is a Markdown file. The frontmatter is optional and its description appears in /help. The body is the prompt and is required.

---
description: Refactor code to pure function
---

Please analyze code in current context, refactor to pure function.
Requirements:

1. Provide refactored code
2. Explain key changes and pure function characteristic implementation
3. Maintain function unchanged

• Put {{args}} where the text you type after the command should go.
• Without {{args}}, your arguments are appended to the end of the prompt after a blank line. With no arguments, the prompt is sent as written.
• Inside a !{...} shell command, {{args}} is shell escaped automatically. With !{grep {{args}} .} in the file, /search "hello" runs grep "hello" .

---
description: Code review based on best practices
---

Review {{args}}, reference standards:

@{docs/code-standards.md}

• @{path} inserts a file. Text files go in as is, images and PDFs are encoded, and binary files may be skipped or cut short. A directory is read recursively and follows .gitignore.
• !{command} runs a shell command and inserts its output. Qwen Code shows a confirmation dialog before the command runs.
• Processing order: @{...} first, then !{...}, then {{args}}.

---
description: Generate Commit message based on staged changes
---

Please generate a Commit message based on the following diff:

```diff
!{git diff --staged}
```

TOML commands with a required prompt field and an optional description still work, but the docs mark the format as deprecated and say it will be removed in a future version. Qwen Code shows a migration prompt when it finds TOML files. Gemini CLI uses the same TOML format, so this matters if you copied commands over from it.

prompt = "Please analyze code: {{args}}"
description = "Code analysis tool"

• Compare: custom slash commands in every AI coding agent
• Gemini CLI custom commands (TOML)
• Qwen Code settings.json, providers and approval modes