GitHub commands

Replace <app-handle> with the GitHub App slug configured for this Tasuku instance.

Issue planning

Preferred trigger when the bot can be assigned:

Assign the issue to the GitHub App bot

Fallback trigger:

Add the label tasuku:plan

Tasuku acknowledges an accepted trigger with an eyes reaction and publishes a structured plan.

Approve issue implementation

@<app-handle> implement

Example:

@acme-reviewer implement

Tasuku resolves the latest applicable plan for the same repository and issue or pull request. If no current plan is available, implementation does not start.

Pull request conversation

Top-level comment:

@<app-handle> <request>

Inline review reply:

@<app-handle> <request about this line or thread>

Explicit commands must begin with the mention. Inline requests retain file, line, diff, and parent-comment context.

The configured Codex or Claude agent evaluates the request with the pull request and repository context. Questions, design discussion, and requests for an opinion receive a direct reply. A clear request to change the code produces a structured plan that waits for approval. Topics unrelated to the pull request receive a scoped reply instead of starting work.

Repositories can optionally enable Automatically handle PR feedback. When enabled, Tasuku performs proportionate read-only investigation of untagged top-level comments, inline review comments, and submitted review bodies from repository owners, members, and collaborators. It also evaluates root inline comments from any external actor GitHub reports as a bot. Tasuku can answer with repository evidence, ask one focused clarification, silently ignore feedback needing no useful response, or prepare a consolidated plan for a clear code change.

Bot text is always treated as untrusted. Bot replies, top-level comments, submitted review bodies, explicit commands, and Tasuku's own comments remain ignored. Inferred feedback is not acknowledged with an eyes reaction and never authorizes implementation.

To bypass that choice and request a plan explicitly:

@<app-handle> plan

Implementation always requires an explicit human command:

@<app-handle> implement

After a successful implementation, Tasuku replies to each originating inline review thread with the commit, the specific change made for that finding, and its agent-reported verification. Tasuku does not resolve an external reviewer's thread; the reviewer or a human decides whether the response is satisfactory.

Approval, cancellation, and retry

An accepted command creates durable workflow state. Cancellation affects pending or active work when its state permits; it does not undo GitHub effects already published. Transient failures can retry with recorded attempts. Before repeating a command, inspect the workflow to avoid duplicating an effect that completed before a later failure.