Slash Commands

Trigger specific actions with /jasper commands in any PR comment.

Available Commands

Use these commands in any pull request comment to trigger specific Jasper actions:

/jasper explain Understanding

Get a detailed explanation of what the PR does. Perfect for understanding complex changes or onboarding new reviewers.

Output includes: Overview, key changes by file, logic flow, dependencies, testing considerations
/jasper improve Enhancement

Get concrete suggestions for improving code quality, performance, and maintainability.

Analyzes: Code quality, performance, best practices, maintainability, edge cases
/jasper security Security

Perform a deep security analysis of the code changes. Identifies vulnerabilities and provides remediation guidance.

Checks for: Injection vulnerabilities (SQL, XSS, command), auth issues, data exposure, input validation, insecure configurations
/jasper summary Documentation

Generate a comprehensive PR summary suitable for the PR description or release notes.

Includes: Title, summary, changes list, technical details, testing notes, breaking changes, dependencies
/jasper review Full Review

Trigger a complete code review covering all aspects: correctness, security, performance, and code quality.

Provides: Verdict (approve/request changes/comment), summary, findings by severity, positive notes
/jasper help Help

Display a list of all available commands with descriptions. Useful for quick reference.

Note: This command doesn't consume a review credit

Usage Examples

Basic Usage

Simply type a command in any PR comment:

/jasper explain

With Additional Context

Add specific focus areas after the command:

/jasper explain the authentication flow
/jasper improve focus on database queries
/jasper security check the file upload handling

Alternative Syntax

You can also use the @jasper mention with commands:

@jasper explain
@jasper /jasper security

Command Output

Each command produces a detailed response tailored to its purpose. Responses are formatted in Markdown with clear sections, code examples where relevant, and actionable recommendations.

Credit Usage

Each slash command (except /jasper help) consumes one review credit from your organization's balance.

Best Practices

  • Use /jasper security for sensitive changes - Authentication, payments, file handling, API endpoints
  • Use /jasper explain for complex PRs - Help reviewers understand large or intricate changes
  • Use /jasper improve before merging - Get final suggestions for polish
  • Use /jasper summary for release notes - Generate consistent PR descriptions

Combining with Chat

After running a slash command, you can follow up with questions using @jasper: 

/jasper security
... (Jasper posts security analysis)

@jasper Can you explain the SQL injection risk in more detail?
... (Jasper provides more context)

See Chat with Jasper for more on interactive conversations.

Chat with Jasper Inline Comments