Pull request change requests
Ask Tasuku to investigate or implement changes from pull request comments.
By default, a request must begin with the configured GitHub App mention. A repository can opt into investigating and responding to untagged feedback with Automatically handle PR feedback in its GitHub automation settings.
Top-level comments
Start the comment with the App handle:
@acme-reviewer update the parser to preserve trailing commentsTasuku records the GitHub actor, repository, pull request, comment, and request text before creating a task. The request executes against the pull request context in an isolated sandbox.
Inline replies
An inline review-thread reply also must begin with the App mention. Tasuku preserves the file, line, diff hunk, and parent review-comment context so the agent can respond to the specific concern.
@acme-reviewer handle this case without allocating a second bufferUntagged feedback
When automatic feedback handling is enabled, Tasuku evaluates untagged top-level comments, inline review comments and replies, and submitted review bodies from GitHub actors associated with the repository as an owner, member, or collaborator. It also accepts root inline review comments from every external actor GitHub identifies as a bot. Missing or untrusted human associations are ignored.
Tasuku performs proportionate read-only investigation using the pull request, repository context, history, tests, and safe diagnostics, then chooses one outcome:
- a clear, actionable change request produces a consolidated plan;
- a direct PR question receives an answer, while a plausible but underspecified change request receives one focused clarification;
- praise, acknowledgements, chatter, and unrelated comments are silently ignored.
Bot replies, bot top-level comments, bot submitted-review summaries, bot commands, and Tasuku's own comments are ignored. Bot feedback is untrusted external text. Inferred interactions do not receive an eyes reaction and cannot start implementation.
Approve the current applicable plan from either context with:
@acme-reviewer implementPublication boundary
The sandbox cannot post a reply or mutate the branch directly. It returns structured output or a bounded changed-file artifact. The worker validates and publishes through the App identity.
Non-triggers
Tasuku ignores:
- comments that merely mention the App later in a sentence;
- comments without the configured App handle when automatic feedback handling is disabled;
- untagged comments from outside collaborators or actors without a trusted GitHub association;
- bot feedback outside a root inline review comment;
- requests on paused or inaccessible repositories;
- duplicate webhook deliveries;
- unsupported comment or actor contexts.
Conversation history
Each accepted mention or inferred interaction creates an interaction record with its source comment and resulting workflow. The pull request detail page shows the stored GitHub conversation, including inferred provenance, beside review findings and runs.