> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/ai-architect/agent-skills.md).

# Agent skills

AI Architect comes with a set of Agent Skills — each one built to handle a specific engineering task like feasibility analysis, epic planning, or production triage. You can trigger them in Jira before coding starts, inside your coding agent while you're building, or in Slack.

Agent skills are structured instruction files that enhance your AI coding assistant with specialized capabilities. In coding agents, skills are installed automatically by the [install scripts](/ai-architect/quick-mcp-integration-with-ai-coding-agents.md) and are discovered dynamically from a `skills/manifest.json` file. Whereas, in Jira, skills are available from Bito Cloud.

Every skill has full context of your codebase and your team's Jira history, so the output reflects how your system actually works.

## All available skills

| Skill                         | Trigger phrases                                                                                              | Description                                                                                                                                                                                                                                                                    |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **bito-codebase-explorer**    | "explain this service", "how does X work", "what does Y depend on", "show me the architecture", "onboard me" | Explore and explain the codebase at any depth for any audience — executive summary to line-level traces                                                                                                                                                                        |
| **bito-build-plan**           | "plan this work", "break down this ticket", "create plan from story"                                         | Convert any unit of work (story, ticket, feature brief, epic, PRD) into a sprint-ready implementation plan with effort estimates                                                                                                                                               |
| **bito-feasibility**          | "is this feasible", "go/no-go on", "what's the blast radius", "trade-off analysis"                           | Go/no-go feasibility and impact analysis — viability, blast radius, effort, dependencies, risks, alternatives                                                                                                                                                                  |
| **bito-spike**                | "spike on", "investigate whether", "explore options for", "proof of concept for"                             | Time-boxed technical investigation — delivers findings and recommendations, not a plan                                                                                                                                                                                         |
| **bito-feature-plan**         | "plan a feature", "design implementation for"                                                                | Detailed org-specific implementation plan for a complex feature using cross-repo context                                                                                                                                                                                       |
| **bito-prd**                  | "write a PRD", "product requirements for"                                                                    | Comprehensive Product Requirements Document grounded in real system context                                                                                                                                                                                                    |
| **bito-trd**                  | "write a TRD", "technical requirements for"                                                                  | Technical Requirements Document analyzing existing architecture, dependencies, and patterns                                                                                                                                                                                    |
| **bito-production-triage**    | "production issue", "incident triage", "debug outage"                                                        | Diagnose production incidents — cross-repo context, blast radius mapping, structured remediation plan                                                                                                                                                                          |
| **bito-code-review**          | "review this PR", "review this MR", "review this branch", "review commit abc123", "review my staged changes" | Read-only code review on any target — PR/MR URL, branch, commit or commit range, local changes (staged / unstaged / all), specific files, or a diff/patch file. Returns severity-rated findings with `file:line` evidence and cross-repo impact. Never commits.                |
| **bito-commit-review**        | "review my changes", "pre-commit review", "check my changes"                                                 | <p>Pre-commit code review analyzing all changes (staged and unstaged) for issues and cross-repo impact.<br><br>It's like a pre-commit gate on your local changes — blocks the commit if there are blocking issues, asks before proceeding, and creates the commit on pass.</p> |
| **bito-plan-to-coding-tasks** | "turn this plan into coding tasks", "make this implementable by an agent"                                    | Transform an implementation plan into self-contained workstream coding tasks                                                                                                                                                                                                   |
| **bito-coding-task-executor** | "execute this coding task", "implement this workstream coding task"                                          | Execute a workstream coding task with verification gates + two-stage review                                                                                                                                                                                                    |

{% hint style="info" %}
**`bito-code-review` vs `bito-commit-review`**

* **`bito-code-review`** reviews any target (PR/MR, branch, commit, local changes, diff file) and produces a report. It's read-only and never commits.
* **`bito-commit-review`** is a pre-commit gate on your local changes. It blocks the commit if there are blocking issues, and creates the commit on pass.

In short: `bito-code-review` reviews anything, anywhere. `bito-commit-review` gates right before committing.
{% endhint %}

### Code review — supported targets

The `bito-code-review` skill is runtime-agnostic — it works in Slack, in your coding agent (Claude Code, Cursor, GitHub Copilot, Windsurf, Junie), and anywhere the Bito skill runtime has shell and `git` access. The same trigger phrases work everywhere.

**What it can review**

<table><thead><tr><th width="240">Target</th><th>How to invoke</th></tr></thead><tbody><tr><td>GitHub PR / GitLab MR / Bitbucket PR</td><td>Paste the URL</td></tr><tr><td>Branch</td><td><code>review the auth-refactor branch</code> — repo is auto-resolved from the thread, a linked ticket, or AI Architect. If none resolve, Bito will ask. You can always specify <code>repo + branch</code> explicitly.</td></tr><tr><td>Single commit</td><td><code>review commit abc123</code></td></tr><tr><td>Commit range</td><td><code>review commits abc123..def456</code></td></tr><tr><td>Local changes</td><td><code>review my staged changes</code> / <code>review unstaged changes</code> / <code>review all my local changes</code></td></tr><tr><td>Specific files</td><td><code>review src/auth/service.ts and src/auth/middleware.ts</code></td></tr><tr><td>Diff or patch file</td><td>Attach the file and ask Bito to review it</td></tr><tr><td>Re-review</td><td><code>verify again</code> after applying fixes</td></tr></tbody></table>

**Flags**

* `--focus security|performance|correctness` — narrow the review to a specific concern
* `--depth quick|standard|deep` — trade depth for latency, or vice versa

**Repository requirements**

Any repository the skill can get code for works:

* **Local targets** use your working directory — no indexing required.
* **Remote targets** work with any repo Bito can clone via your `git` auth.

{% hint style="info" %}
AI Architect indexing is **not required** for code review. When it's set up, Bito enriches the review with cross-repo impact analysis; without it, the review degrades gracefully and still runs.
{% endhint %}

## How to invoke skills

#### In Jira

Agent skills can be triggered on demand on Epic or Story by commenting:

```
@bito turn this epic into tasks
@bito technical plan for this PRD
```

<a href="/pages/T3t60cgwTuhayIP54mlb" class="button primary">Integrating with Jira</a>

#### In Slack

Agent skills are also available directly in Slack via the [**Bito AI Assistant** app](/ai-architect/integrating-ai-architect-with-your-tools/integrating-with-slack.md). Mention `@Bito` in any channel and describe what you need. It will activate the right skill automatically.

```
@Bito is this feasible
@Bito turn this plan into agent specs
@Bito execute this agent spec
```

<a href="/pages/lBKzyKNiaVbnJqBVAIeo" class="button primary">Integrating with Slack</a>

#### In your coding agent

Once AI Architect is connected via MCP, skills are available in compatible coding agents. Describe what you need in natural language and the agent activates the right skill automatically — or invoke one directly by name. You can type `/` in the chatbox to see the list of available skills and select one interactively.

<a href="/pages/ukXGFlvfYqskwfVSaPqO" class="button primary">Integrating with coding agents</a>

<figure><img src="/files/mEwdE8wI0XHyrFUc45Cx" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/PRwjVhvnuwBCnRuo6YEX" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/T33fHchlKeE0QGswMTCq" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/d2FIDewvxCWtLUWFeBEC" alt=""><figcaption></figcaption></figure>

## Skills installation locations:

<table><thead><tr><th width="188.20001220703125">IDE</th><th>Location</th><th>Format</th></tr></thead><tbody><tr><td>Claude Code</td><td><code>~/.claude/skills/bito-{name}/SKILL.md</code></td><td>Markdown with YAML frontmatter</td></tr><tr><td>Cursor</td><td><code>~/.cursor/rules/bito-{name}.mdc</code></td><td><code>.mdc</code> with <code>alwaysApply: false</code></td></tr><tr><td>Windsurf</td><td><code>~/.codeium/windsurf/memories/bito-{name}.md</code></td><td>Plain markdown</td></tr><tr><td>VS Code (GitHub Copilot)</td><td><code>{User}/prompts/bito-{name}.prompt.md</code></td><td><code>.prompt.md</code> with <code>applyTo</code></td></tr><tr><td>Junie</td><td><code>~/.junie/skills/bito-{name}/SKILL.md</code></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bito.ai/ai-architect/agent-skills.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.