Interacting with the Bot

There are four ways to trigger the bot from GitHub.

A. Assign an issue

Open an issue describing what you want and assign vgvbot as the assignee. The bot replies with an acknowledgement, drafts the change, and pushes a PR that closes the issue.

If a PR for that issue already exists, the bot tells you and points to it instead of opening a duplicate.

B. Mention the bot in a comment

On any issue or PR, post a comment starting with @vgvbot followed by what you want.

You write something like…	The bot does
`@vgvbot what does this function do?`	Analyze — answers in a comment. No code changes.
`@vgvbot fix the failing test in user_service.ts`	Open a PR with the fix.
`@vgvbot please address the review` (on a PR)	Address review — reads open review comments and pushes commits that resolve them.
`@vgvbot review this PR` (on a PR)	Code review — leaves inline review comments on the diff.
`@vgvbot rebase this PR onto main` (on a PR)	Rebase the PR onto its base branch, resolving conflicts where safe.
`@vgvbot merge main into this PR` (on a PR)	Merge the base branch into the PR, resolving conflicts where safe.
`@vgvbot ping`	Replies `pong` — quick health check.

Slash commands

For common actions, use a slash command instead of free-form text. Slash commands skip the intent analyzer and trigger the same behavior with a consistent template across the team.

Command	What it does
`@vgvbot /review-pr`	Code review focused on nits and readability (PR only).
`@vgvbot /summarize`	Summarize the changes in this issue or PR.
`@vgvbot /address-review`	Address open review comments (PR only).
`@vgvbot /rebase`	Rebase the PR onto its target branch (PR only).
`@vgvbot /merge`	Merge the target branch into this PR (PR only).
`@vgvbot /help`	List available slash commands.

You can append free-form text after a slash command for extra context — for example, @vgvbot /review-pr focus on error handling.

Rules to keep in mind

For rebase / merge, be explicit about the strategy. “Resolve the conflicts” without rebase or merge will not work — the bot will ask which one you mean.
Address-review, code-review, rebase, and merge only work on pull requests. Asking on an issue gets a polite refusal.
Only repo admins, maintainers, and users on the interaction-users allowlist can trigger the bot. Comments from anyone else are ignored.

C. Request a review from the bot on a PR

In the GitHub PR sidebar, add vgvbot as a reviewer. The bot acknowledges in a comment, runs a code review, and posts inline comments tied to the diff.

D. Resolve review comments to trigger auto-approval

When the bot leaves inline review comments, each one becomes a conversation thread on the PR. As you address feedback, click Resolve conversation on each thread.

Once every thread the bot opened is resolved, the bot submits a formal Approve review automatically. No need to ask for a second pass.

One exception: if the bot opened the PR itself, GitHub does not allow self-approval. In that case the bot posts an acknowledgement comment instead.

See Auto-Approve for the full rules.

Quick reference

# On an issue:
@vgvbot Implement a dark mode toggle in settings.

# On a PR:
@vgvbot please address the review
@vgvbot review this PR
@vgvbot rebase this PR onto main
@vgvbot merge main into this PR

# Slash commands (on an issue or PR):
@vgvbot /review-pr
@vgvbot /summarize
@vgvbot /address-review
@vgvbot /rebase
@vgvbot /merge
@vgvbot /help

# Anywhere:
@vgvbot ping

You can also just assign the bot to an issue directly — no comment needed.