> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger with Slash Command

> Launch a workflow when a repository comment or Jira issue comment includes a custom slash command such as /review.

This guide walks through creating a Workflow that starts when someone types a **slash command** (`/review`) in a comment. The flow will clone the repository and open an agent session to review the pull request or handle the Jira issue.

***

## Create a Workflow

<Steps>
  <Step title="Open the Workflows page">
    From the main menu, click <code>Workflows</code> and then select <code>Create Workflow</code>.
  </Step>

  <Step title="Name the Workflow">
    Give the Workflow a descriptive name such as <code>PR Review via Slash Command</code> or <code>Jira Issue Review via Slash Command</code>.
  </Step>
</Steps>

***

## Configure the Slash Command Trigger

<Steps>
  <Step title="Edit the default trigger or add a new manual trigger">
    Click an existing Trigger or click on "Add Trigger" to create a new one.
  </Step>

  <Step title="Select Manual event type">
    Choose <code>Manual</code> from the Trigger Event selector.
  </Step>

  <Step title="Enter the command text">
    In the <code>SlashCommand</code> field, type <code>review</code>. Do **not** include the leading slash character.
  </Step>

  <Step title="Decide if a mention is required (optional)">
    Enable <code>Require Mention</code> if the command should only trigger when it follows <code>@overcut</code>. Example trigger text: <code>@overcut /review</code>.
  </Step>

  <Step title="Note about execution timing">
    Slash command triggers always execute immediately when detected, ensuring responsive user interaction. Delay settings are not applicable for this trigger type.
  </Step>
</Steps>

<Note>
  The trigger listens to comments on pull requests, issues, and review threads in **GitHub**, **GitLab**, and **Bitbucket**, as well as comments on **Jira tickets**. In those surfaces the command appears at the start of a line (or after `@overcut` if `Require Mention` is enabled). It also works in **registered Slack channels**, where the syntax is `/overcut <command>`: the token after the `/overcut` bot prefix is what matches the SlashCommand field. For Slack setup, see [Slack integration](/docs/integrations/slack).
</Note>

## Slash Command Usage Patterns

Slash commands can be configured in two ways:

### 1. **Manual-Only Trigger**

When you add **only** the manual trigger with the Slash Command field, the workflow will **only** run when someone explicitly types the command. This creates a completely manual workflow that gives users full control over when it executes.

**Use cases:**

* On-demand code reviews
* Manual issue analysis
* User-initiated documentation generation
* Custom workflow execution

### 2. **Hybrid Trigger (Automatic + Manual)**

You can combine slash commands with other automatic triggers to create hybrid workflows. For example:

* **Issue labeled + Slash command**: Automatically process labeled issues, but also allow manual `/review` commands
* **PR opened + Slash command**: Start workflows on PR creation, but also support manual `/analyze` commands

**Benefits:**

* Automatic processing for common scenarios
* Manual override capability when needed
* Flexible workflow control
* User empowerment without losing automation

<Note>
  Slash command executions always take precedence over other running manual workflows. When a user invokes the command, the new run starts immediately with the parameters provided in the comment.
  see [Trigger Execution](/docs/reference/trigger-execution) for more details.
</Note>

***

## Test the Workflow

<Steps>
  <Step title="Trigger from a supported surface">
    **GitHub**: In the pull request conversation, type <code>/review</code> (or <code>@overcut /review</code> if a mention is required).

    **Jira**: In the issue comments, type <code>/review</code> (or <code>@overcut /review</code> if a mention is required).

    **Slack**: In a [registered channel](/docs/integrations/slack#register-channels-in-a-project), type <code>/overcut review</code>. Slack always uses <code>/overcut</code> as the bot prefix; the token after it (<code>review</code>) is what matches the SlashCommand field on this trigger. A plain <code>@overcut</code> mention fires a separate **mention** trigger, not this slash-command trigger.
  </Step>

  <Step title="Watch the Execution">
    A new execution appears on the <code>Executions</code> page. The agent responds in the source surface based on your workflow setup.
  </Step>
</Steps>

***

## Supported Platforms

Slash commands work across Overcut integrations that support text-based workflow triggers:

* **GitHub**: Pull requests, issues, and review threads
* **Jira**: Issue comments and descriptions
* **GitLab**: Issues, merge requests, and comments
* **Bitbucket**: Issues, pull requests, and comments
* **Azure DevOps**: Work items and pull requests
* **Slack**: Registered channels, through `/overcut <command>` or `@overcut /<command>`

<Note>
  Syntax depends on the surface. Repository and ticket comments match the command string you configured on the trigger (for example, `/review` or `@overcut /review`). Slack uses the bot's built-in slash command, `/overcut <command>`; the token after `/overcut` is what matches the SlashCommand field on your trigger. A plain `@overcut` mention in Slack fires a separate **mention** trigger, not the slash-command trigger covered here.
</Note>

***

## ✅ Success Checklist

<ol>
  <li>The workflow triggers on the configured command or mention</li>
  <li>The workflow executes successfully</li>
  <li>Works consistently across GitHub, GitLab, Bitbucket, Azure DevOps, Jira, and registered Slack channels</li>
</ol>