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

# Commands

> Use Propel commands in pull requests to run reviews, capture knowledge, and create follow-up tickets.

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.

<img src="https://mintcdn.com/propelplatforminc/lVvw00YxwnzW9WA9/images/user-guide/propel-review-comment.png?fit=max&auto=format&n=lVvw00YxwnzW9WA9&q=85&s=1859e51b71ac778d3a2e1e62c52346a5" alt="Screenshot of a GitHub pull request comment using /propel review." width="1870" height="331" data-path="images/user-guide/propel-review-comment.png" />

<Note>
  Add commands directly in the pull request conversation.
</Note>

## Core commands

| 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 |

## Command examples

Run a fresh review:

```bash theme={null}
/propel review
```

Resolve old threads and run a clean pass:

```bash theme={null}
/propel clean review
```

Save a reusable rule:

```bash theme={null}
/propel add to knowledge base "Use CompanyId instead of CompanyID across services"
```

Create a ticket from an inline finding:

```bash theme={null}
/propel create-ticket Capture this bug and include a rollback plan
```

## Natural language requests

Propel also supports natural language requests in pull request comments.

Examples:

* `@propel remember always validate external payloads before writes`
* `add test case for null and empty inputs`

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

## Troubleshooting

* 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](/features/linear-integration).
* If commands are ignored, confirm you posted them as pull request comments and not in an unrelated thread.

## Next steps

1. Configure ticket destinations in [Ticket destination](/features/ticket-destination).
2. Capture reusable guidance in [Knowledge base](/features/knowledge-base).
3. Review behavior in [Review settings](/features/workflows).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.