Skip to main content
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:
CommandDescription
summarizeSummarize discussions and key decisions
documentGenerate documentation from content
planCreate implementation plans
design-docGenerate design documents
prototypeCreate prototype specifications
diagnoseAnalyze and diagnose problems
postmortemGenerate postmortem analysis
insightsExtract key insights
changelogGenerate changelog entries
reportCreate status reports
review-prepPrepare for review meetings
relatedFind related issues
impactAnalyze potential impact

Creating Custom Action Types

1

Navigate to Action Types

Go to Settings → Templates → Action Types
2

Click Create

Click the Create Action Type button
3

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
4

Save

Click Save to create your custom action type

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
Custom action types are organization-wide. Any team member can use them once created.