Interactive PRs conversations

Blame isn’t just a static review bot. Developers can converse with Blame directly within GitHub pull request discussion threads and inline diff comment threads by tagging @blame or using slash commands. Whether you need clarification on a suggested fix, want to ask how a diff interacts with a legacy backend service, or want to trigger a fresh review run, Blame responds natively in your GitHub conversation.

Conversing with `@blame` on GitHub

You can tag @blame anywhere on GitHub pull requests:

Top-Level PR Discussion Comments (issue_comment): Ask high-level architectural questions about the overall pull request.
Inline Diff Threads (pull_request_review_comment): Ask specific questions anchored to a file path, line number, or diff hunk.

@blame Can you explain why you suggested wrapping the token decode in a try/catch here?

Will this catch invalid signature errors from jsonwebtoken?

How Blame Resolves PR Context

When you tag @blame, Blame’s webhook handler reconstructs the full context surrounding your comment before invoking the chat agent:

Context Elements Passed to the Agent

Exact File & Line: Identifies the specific file path (comment.path) and line number (comment.line).
Diff Hunk: Provides the surrounding lines of added/removed code (comment.diff_hunk).
Thread History: Pulls the last 5 comments from the thread so multi-turn conversations stay coherent.
Codebase Index: The agent queries the repository’s Tree-sitter vector graph to check definitions across other files.

Available Slash Commands

You can execute review actions directly by posting slash commands in the PR comment box:

Command	Action	Example Use Case
`/blame review` or `/review`	Triggers an immediate, full adversarial code review run across the pull request.	Re-evaluate the PR after addressing feedback or pushing external fixes.
`@blame explain`	Explains the intent, logic flow, and architectural implications of the diff.	Quick onboarding for reviewers unfamiliar with a specific subsystem.
`@blame suggest-tests`	Analyzes the diff and outputs concrete unit or integration test cases to write.	Ensuring comprehensive test coverage before merging.
`@blame simplify`	Suggests refactored versions of the modified code to improve readability and maintainability.	Cleaning up verbose or over-engineered implementations.

Inline Thread Discussions

When Blame leaves an inline finding with a 1-click suggestion, developers can reply directly in that comment thread to debate or refine the solution:

<!-- Developer Reply -->

@blame If we use your suggestion, won't `cachedUser` be undefined when Redis is down?

How should we handle cache fallbacks?

Blame evaluates the comment, inspects your cache fallback utility in the codebase graph, and replies with a hardened snippet directly in the same thread.

Webhook Security & Execution Flow

Zero Polling: Blame listens asynchronously to GitHub issue_comment and pull_request_review_comment events via signed HMAC webhooks (x-hub-signature-256).
Installation Scoping: Permissions and repository access tokens are automatically verified using the GitHub App installation credentials for your workspace.
Fast Response: Chat agent reasoning is queued immediately to deliver replies back to GitHub within seconds.

Review Architecture & Anatomy — Detailed breakdown of PR summary comments and inline suggestions.
CI/CD Quality Gates & Status Checks — Enforcing status check criteria in branch protection rules.
AI Chat & Codebase Memory — Interactive multi-repo web chat interface.

Getting Started

Code Review

Account

How Blame Works

Interactive PRs conversations

Conversing with `@blame` on GitHub

How Blame Resolves PR Context

Context Elements Passed to the Agent

Available Slash Commands

Inline Thread Discussions

Webhook Security & Execution Flow

​Conversing with @blame on GitHub

​How Blame Resolves PR Context

​Context Elements Passed to the Agent

​Available Slash Commands

​Inline Thread Discussions

​Webhook Security & Execution Flow

​Related Documentation

Conversing with `@blame` on GitHub

How Blame Resolves PR Context

Context Elements Passed to the Agent

Available Slash Commands

Inline Thread Discussions

Webhook Security & Execution Flow

Related Documentation