Commands

Use this page as the source of truth for Propel command syntax.

Where commands work

Add commands in pull request comments.
Use inline code comments when you want to create a follow-up ticket.
Use general pull request comments for review, clean review, and knowledge capture commands.

Add commands directly in the pull request conversation.

Command	What it does	Where to run it
`/propel review`	Triggers a code review run for the pull request.	General pull request comment
`/propel clean review`	Resolves existing review threads, then runs a fresh review.	General pull request comment
`/propel add to knowledge base "<rule>"`	Saves a rule so Propel can apply it in future reviews.	General pull request comment
`/propel create-ticket <instructions>`	Creates a follow-up ticket from a specific finding.	Inline code comment
`@auto`	Auto-generates the pull request title.	Pull request title
`{ticket_id} @auto`	Auto-generates the title and keeps your ticket ID prefix.	Pull request title

Run a fresh review:

/propel review

Resolve old threads and run a clean pass:

/propel clean review

Save a reusable rule:

/propel add to knowledge base "Use CompanyId instead of CompanyID across services"

Create a ticket from an inline finding:

/propel create-ticket Capture this bug and include a rollback plan

Propel also supports natural language requests in pull request comments. Examples:

Propel classifies these requests and routes them to the right action.

If /propel create-ticket fails, confirm your default destination is configured in Administration -> Settings -> Tickets.
If ticket creation fails for Linear, reconnect in Linear integration.
If commands are ignored, confirm you posted them as pull request comments and not in an unrelated thread.