Skip to main content
Extensions

Commands

Use / to invoke reusable workflows, or save recurring task requirements as custom commands.

When you regularly prepare handoffs, review changes, or produce results in a fixed format, save those requirements as a Command. Select it with / in the task composer, then add what you need done this time to reuse the same instructions. Commands can come from installed plugins or Markdown files you write yourself.

Find available commands

Open Settings → Extension management → Commands to review commands supplied by plugins, including their names, descriptions, and providers. To use a plugin's commands, first install and enable the plugin under Extensions → Plugins. Type / in the task composer, followed by a name or keyword, and look for a command entry. Custom project commands are available in that project's workspace. Save requirements you reuse across projects as user commands.

Use a command in a task

  1. Open a task. For a project command, first confirm that the task uses the corresponding workspace.
  2. Type / and a name or keyword. Use the Up and Down arrow keys to choose a candidate, then press Enter or Tab to add it.
  3. After the command item, add the goal, scope, and materials for this request, then send the message.
  4. Review the result against the command's requirements. Continue in the same task if you need to adjust it.
For example, with the GitLab plugin installed and enabled, type /pipeline, select gitlab:pipeline-status, and specify the project and pipeline to check. Commands that use an external service also require authentication for the relevant connector. If selecting a command alone produces a reply without starting the work, add an explicit request, such as “Use this command to prepare a handoff for the current task.”

Create a custom command

Choose where the command should be available, then save a Markdown file in the corresponding directory. Create the directory if it does not exist.
ScopeDirectorySuitable content
User~/.qoder/commands/Requirements you reuse across workspaces
Project<project>/.qoder/commands/Conventions or workflows for tasks in that project's workspace
~ represents your home directory. For example, create handoff.md with the following content: 
---
description: Prepare a task handoff
---

Summarize the work in the current conversation under Completed, Validation, and Open items.
Include only supported results. Do not describe plans or unverified work as completed.
The filename without .md is the command name. description appears in the candidate list, and the body contains the task instructions to reuse. Choose a short, recognizable name so it is easy to find in the composer. Save the file, open a new task, and type /handoff. Select the command and add “Prepare a handoff for this task, including unfinished items.” Use @ to add any other materials you need; see Send messages.

Update or remove a command

Custom commands live in your Markdown files. To change the requirements, edit and save the file, then reopen the / list in a new task to check the result. To remove a command, move its file out of the commands directory and confirm that it no longer appears. Manage commands supplied by a plugin through their parent plugin. To change their availability, use plugin management.

Troubleshoot commands

  • Plugin commands: confirm that the plugin is installed and enabled, then search by name or keyword. Names may include a plugin prefix, such as gitlab:pipeline-status.
  • Project commands: confirm that the task uses the project's workspace and that the file is in its .qoder/commands/ directory.
  • User commands: check the user directory in the table above, the .md extension, and that the file contains the instructions to execute.
After saving a file or changing a plugin, close the candidate list and type / again. If the command is still missing, check again in a new task.