The approve plugin implements a pull request approval process that manages the 'approved' label and an approval notification comment.

The assign plugin assigns or requests reviews from users/teams.

The backport validation plugin is used to validate that backports come from merged PRs in a configured upstream repository.

The blunderbuss plugin automatically requests reviews from reviewers when a new PR is created.

The cherrypick plugin is used for cherrypicking PRs across branches.

The help plugin provides commands that add or remove the 'help wanted' and the 'good first issue' labels from issues.

The hold plugin allows anyone to add or remove the 'do-not-merge/hold' Label from a pull request in order to temporarily prevent the PR from merging without withholding approval.

The Jira plugin links Pull Requests and Issues to Jira issues

The label plugin provides commands that add or remove certain types of labels.

The lgtm plugin manages the application and removal of the 'lgtm' (Looks Good To Me) label which is typically used to gate merging.

Close, reopen, flag and/or unflag an issue or PR as frozen/stale/rotten

The multi-pr-prow-plugin triggers the requested test against source(s) built from the origin PR and the requested additional PRs

The needs-rebase plugin manages the 'needs-rebase' label by removing it from Pull Requests that are mergeable and adding it to those which are not.

The override plugin allows repo admins to force a github status context to pass

The payload-testing plugin triggers a run of specified release qualification jobs against PR code

The refresh plugin is used for refreshing status contexts in PRs.

The retitle plugin allows users to re-title pull requests and issues where GitHub permissions don't allow them to.

The size plugin manages the 'size/*' labels, maintaining the appropriate label on each pull request as it is updated.

The skip plugin allows users to clean up GitHub stale commit statuses for non-blocking jobs on a PR.

The transfer-issue plugin transfers a GitHub issue from one repo to another in the same organization.

The trigger plugin starts jobs in reaction to various events.

The verify-owners plugin validates OWNERS and OWNERS_ALIASES files (by default) and ensures that they always contain collaborators of the org, if they are modified in a PR.

The wip (Work In Progress) plugin applies the 'do-not-merge/work-in-progress' Label to pull requests whose title starts with 'WIP' or are in the 'draft' stage, and removes it from pull requests when they remove the title prefix or become ready for review.