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

# Action Types

> Create custom @kasava commands for your organization

Navigate to **Settings → Templates → Action Types** to create custom `@kasava` commands for your organization.

## What Are Action Types?

Action types define the commands available when team members use `@kasava` mentions in GitHub issues, Linear issues, Asana tasks, and other connected platforms. Kasava includes built-in action types, and you can create custom ones for your organization's specific workflows.

## Built-in Action Types

These commands are available to all organizations:

| Command       | Description                             |
| ------------- | --------------------------------------- |
| `summarize`   | Summarize discussions and key decisions |
| `document`    | Generate documentation from content     |
| `plan`        | Create implementation plans             |
| `design-doc`  | Generate design documents               |
| `prototype`   | Create prototype specifications         |
| `diagnose`    | Analyze and diagnose problems           |
| `postmortem`  | Generate postmortem analysis            |
| `insights`    | Extract key insights                    |
| `changelog`   | Generate changelog entries              |
| `report`      | Create status reports                   |
| `review-prep` | Prepare for review meetings             |
| `related`     | Find related issues                     |
| `impact`      | Analyze potential impact                |

## Creating Custom Action Types

<Steps>
  <Step title="Navigate to Action Types">
    Go to **Settings → Templates → Action Types**
  </Step>

  <Step title="Click Create">
    Click the **Create Action Type** button
  </Step>

  <Step title="Configure the Action Type">
    Fill in the required fields:

    * **Name** - The command name (e.g., `security-review`)
    * **Display Name** - Human-readable name shown in the UI
    * **Keywords** - Alternative trigger words (e.g., `security`, `sec-review`)
    * **Instructions** - AI instructions for how to handle this command
  </Step>

  <Step title="Save">
    Click **Save** to create your custom action type
  </Step>
</Steps>

## Using Custom Commands

Once created, custom commands work identically to built-in ones:

```
@kasava security-review
@kasava my-custom-action
```

Team members can use any configured keywords:

```
@kasava sec-review  # Uses the security-review action type
```

## Managing Action Types

From the Action Types page, you can:

* **View** all built-in and custom action types
* **Edit** custom action types to update instructions
* **Delete** custom action types you no longer need
* **View Instructions** to see the AI prompt for any action type

## Best Practices

1. **Use descriptive names** - Make commands self-explanatory (e.g., `sprint-summary`, `qa-checklist`)
2. **Add helpful keywords** - Include common abbreviations and variations
3. **Write clear instructions** - Provide specific guidance for the AI
4. **Test before sharing** - Try your command on a test issue first

<Tip>
  Custom action types are organization-wide. Any team member can use them once created.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Templates" icon="file-code" href="/docs/account/settings/templates">
    Customize response formatting
  </Card>

  <Card title="Integrations" icon="plug" href="/docs/integrations/overview">
    Connect platforms to use @kasava
  </Card>
</CardGroup>