For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Pre-commit code review analyzing all changes (staged and unstaged) for issues and cross-repo impact. 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.

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

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.

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

Target
How to invoke

GitHub PR / GitLab MR / Bitbucket PR

Paste the URL

Branch

review the auth-refactor branch β€” repo is auto-resolved from the thread, a linked ticket, or AI Architect. If none resolve, Bito will ask. You can always specify repo + branch explicitly.

Single commit

review commit abc123

Commit range

review commits abc123..def456

Local changes

review my staged changes / review unstaged changes / review all my local changes

Specific files

review src/auth/service.ts and src/auth/middleware.ts

Diff or patch file

Attach the file and ask Bito to review it

Re-review

verify again after applying fixes

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.

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.

How to invoke skills

In Jira

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

Integrating with Jira

In Slack

Agent skills are also available directly in Slack via the Bito AI Assistant app. Mention @Bito in any channel and describe what you need. It will activate the right skill automatically.

Integrating with Slack

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.

Integrating with coding agents

Skills installation locations:

IDE
Location
Format

Claude Code

~/.claude/skills/bito-{name}/SKILL.md

Markdown with YAML frontmatter

Cursor

~/.cursor/rules/bito-{name}.mdc

.mdc with alwaysApply: false

Windsurf

~/.codeium/windsurf/memories/bito-{name}.md

Plain markdown

VS Code (GitHub Copilot)

{User}/prompts/bito-{name}.prompt.md

.prompt.md with applyTo

Junie

~/.junie/skills/bito-{name}/SKILL.md

Last updated