Control RepoWarden directly from your pull requests. Comment on any RepoWarden PR to rebase, fix tests, or resolve review comments -- no context switching required.
PR commands let you interact with RepoWarden by commenting on pull requests it has created. Instead of switching to the RepoWarden dashboard, you can manage your PRs without leaving GitHub. Type a command as a comment, and RepoWarden will pick it up and execute it within minutes.
Example workflow
RepoWarden opens a PR to update your dependencies
CI fails because of a breaking change in a new package version
You comment @repowarden fix-tests on the PR
RepoWarden analyzes the CI logs, pushes a fix, and CI goes green
Navigate to any pull request that was created by RepoWarden on your repository.
Type a command like @repowarden rebase in the PR comment box and submit it.
RepoWarden picks up the command, executes it, and replies with the result within minutes.
Each command is triggered by commenting on a RepoWarden pull request. Commands are case-insensitive.
@repowarden rebaseRebases the PR branch onto the latest base branch (usually main). Useful when the PR has fallen behind and needs to be brought up to date with the latest changes.
Example comment
@repowarden rebaseRepoWarden will fetch the latest base branch, rebase the PR branch onto it, and force-push the updated branch. If there are merge conflicts, it will comment back with details so you can resolve them manually.
@repowarden fix-testsAnalyzes CI failures on the PR and attempts to fix failing tests automatically using AI. It reads the CI logs, identifies what went wrong, and pushes a fix commit.
Example comment
@repowarden fix-testsRepoWarden pulls the CI failure logs and annotations, identifies the failing tests, reads the relevant source files, and generates a fix. The fix is pushed as a new commit to the PR branch. If CI passes after the fix, you are good to merge.
@repowarden resolve-commentsReads all unresolved review comments on the PR and attempts to address each one by making the requested code changes.
Example comment
@repowarden resolve-commentsRepoWarden reads each unresolved review comment, understands the requested change in context, and pushes a commit that addresses the feedback. It handles code style suggestions, bug fixes, naming changes, and more. Each resolved comment is addressed in the commit message.
No, PR commands only work on pull requests that were created by RepoWarden. This is by design -- RepoWarden needs to have push access to the PR branch, which it only has for branches it created. If you comment on a PR that was not created by RepoWarden, the command will be ignored.
No. PR commands work automatically once you have the RepoWarden GitHub App installed on your repository. There is no additional setup, CLI tool, or configuration required. Just comment on any RepoWarden PR and the bot will respond.
Most commands complete within 1-3 minutes. Rebase is usually the fastest (under a minute). Fix-tests and resolve-comments may take longer depending on the complexity of the changes needed, as they involve AI analysis of your code.
Yes. You can use any command at any time on a RepoWarden PR. Commands are processed one at a time in the order they are received. Wait for one command to finish before issuing another to avoid conflicts.
If a command cannot complete successfully, RepoWarden will reply to your comment with an explanation of what went wrong. For example, if rebase encounters merge conflicts, or if fix-tests cannot determine the cause of a failure, you will get a clear message describing the issue.
PR commands do not consume additional scan credits. They are included with your plan at no extra cost. However, the PRs themselves count toward your monthly PR limit as usual.
Install the RepoWarden GitHub App, enable your repos, and start using commands on your next PR.