Skip to main content
This guide walks through creating a Use Case 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 Use Case

1

Open the Use Cases page

From the main menu, click Use Cases and then select Create Use Case.
2

Name the Use Case

Give the Use Case a descriptive name such as PR Review via Slash Command or Jira Issue Review via Slash Command.

​
Configure the Slash Command Trigger

1

Edit the default trigger or add a new manual trigger

Click an existing Trigger or click on “Add Trigger” to create a new one.
2

Select Manual event type

Choose Manual from the Trigger Event selector.
3

Enter the command text

In the SlashCommand field, type review. Do not include the leading slash character.
4

Decide if a mention is required (optional)

Enable Require Mention if the command should only trigger when it follows @overcut. Example trigger text: @overcut /review.
5

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.
The trigger listens to comments on pull requests, issues, and review threads in GitHub, GitLab, and Bitbucket, as well as comments on Jira tickets. When the command string appears at the start of a line, Overcut evaluates the workflow.

​
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
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 for more details.

​
Test the Workflow

1

Comment with the slash command

GitHub: In the pull request conversation, type /review (or @overcut /review if a mention is required).Jira: In the issue comments, type /review (or @overcut /review if a mention is required).
2

Watch the Execution

A new execution appears on the Executions page. The agent posts its review as a comment once finished.

​
Supported Platforms

Slash commands work across all platforms that Overcut integrates with:
  • 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
The slash command syntax is consistent across all platforms: /command or @overcut /command. Any platform that supports comments or text content can trigger slash command workflows.

​
✅ Success Checklist

  1. The workflow triggers on the slash command comment
  2. The workflow executes successfully
  3. Works consistently across GitHub, GitLab, Bitbucket, Azure DevOps and Jira integrations