GitHub Issues

Bucky responds to @bucky mentions on GitHub issues. This is the most direct way to trigger a Claude session.

Commands

Comment	Action
@bucky	Run a session — Claude decides what to do (plan, implement, or both)
@bucky /plan	Run in plan-only mode — analyze the issue and post an implementation plan

How it works

Agent-dispatched issues

When the agent service creates a GitHub issue (from Slack or Jira), it dispatches a Claude session automatically. The workflow runs in the target repo and posts results as comments on the issue.

Direct @bucky comments

When you comment @bucky on an existing issue, the GitHub App webhook routes the event to the agent service. The agent reads the issue context and decides how to proceed.

Caution

@bucky comments on issues are handled by the agent service via GitHub App webhooks. This is different from PR comments, which are handled directly by the tag-bucky GitHub Action.

Typical flow

1. Create or find a GitHub issue describing the work
2. Comment @bucky — Bucky reads the codebase, plans the work, implements it, and opens a PR
3. Alternatively, comment @bucky /plan to get just a plan for review first
4. Review the results and provide feedback if needed

Labels

Bucky uses labels to signal status:

Label	Color	Meaning
needs-review	Blue	Plan is ready for human review
needs-attention	Yellow	Missing info or requires human input
error	Red	Something went wrong