BugViper responds to commands posted as comments on any GitHub pull request where the app is installed. Simply mention @bugviper followed by a command, and the bot will respond directly in the PR thread — no external dashboards or context switching required.
Commands only work if BugViper is installed on the repository. If the bot does not respond, ask your repository admin to install the BugViper GitHub App.
Commands Reference
Type @bugviper help on any PR to see a list of commands posted directly by the bot in the PR thread.
@bugviper review vs @bugviper full review
Both commands trigger an AI-powered code review, but they differ in scope.
@bugviper review performs an incremental review — it inspects only the files that were changed in the most recent push to the PR. This is the right choice for most day-to-day use: it’s fast, focused, and avoids re-reviewing code the bot has already seen.
@bugviper full review performs a full diff review — it re-examines every changed file in the entire PR from top to bottom, regardless of what was reviewed before. Use this when:
- You’ve made substantial changes across many files and want a fresh perspective on the whole PR.
- You suspect an earlier incremental review missed something due to a partial diff.
- You’re doing a final pass before merging a long-running feature branch.
As a general rule, reach for @bugviper review during active development and save @bugviper full review for pre-merge or after major rebases.
@bugviper run lint
The run lint command triggers BugViper’s static analysis mode — a fast, deterministic check that runs popular linting tools against the PR’s changed files. Unlike the AI review commands, lint mode does not spin up any AI agents, making it significantly faster to complete.
BugViper automatically selects the right tool for each file type it encounters:
- ESLint for JavaScript and TypeScript files
- Ruff for Python files
- golangci-lint for Go files
After the run, BugViper posts inline comments for any lint findings and a summary of issues found per tool. This makes @bugviper run lint a great fit for CI-style checks — catching style violations, formatting issues, and common code smells before a human reviewer ever looks at the PR.
To learn how to enable, disable, or configure each tool, see the Tools Configuration guide.
@bugviper resolve
After you’ve addressed BugViper’s feedback, your PR thread can fill up with stale inline review comments. The resolve command lets you clean all of that up in one shot.
Posting @bugviper resolve on a PR tells the bot to resolve all of its own inline review comments on that PR. Use this once you’ve worked through the issues BugViper flagged and want a clean, uncluttered PR view before requesting a human review or merging.
@bugviper resolve only resolves comments posted by BugViper itself — it will not touch comments left by human reviewers or other bots.
@bugviper help
If you ever forget a command or want a quick reference without leaving GitHub, post @bugviper help on any PR. The bot will reply with a formatted list of all available commands directly in the PR thread.