Can Copilot coding agents review their own changes?

Can Copilot coding agents review their own changes before opening a pull request

Yes, but not as a final self-approval step. GitHub Copilot cloud agent can make iterative changes on a branch, and Copilot code review can review a pull request after those changes exist. The useful pattern is to let the agent work, inspect the diff, and then ask for review before you mark the PR ready.

The part people get wrong is treating “Copilot reviewed it” as the same thing as “the agent checked its own work and signed off.” GitHub documents these as two different stages. One stage is the agent creating or updating code on a branch. The other stage is Copilot code review reading that branch and leaving review comments on a pull request.

If you want an early check before opening a PR, the documented workflow is to let Copilot research the repository, create an implementation plan, and make changes on a branch first. GitHub says this lets you review the diff and refine the work before you open a pull request for review. That is the closest supported version of “review before PR.”

Copilot code review itself runs on a pull request. GitHub says you create or open a PR, request Copilot as a reviewer, and then read the comments it leaves. Copilot always leaves a comment review, not an approve or request-changes decision, and those reviews do not count toward required approvals.

That limitation is inconvenient, but it is the important one. If your team needs a required approval gate, Copilot does not provide it. It can surface problems early, suggest fixes, and reduce obvious review noise, but the final decision still belongs to human reviewers and your repository rules.

A practical workflow looks like this: ask Copilot to make changes on a branch, inspect the branch diff yourself, open a draft pull request, request Copilot review, fix the obvious issues, then mark the PR ready for human review. GitHub also documents that draft PR reviews can be used as an early check before you request a review from your team.

The part that usually causes trouble is automatic re-review. GitHub says Copilot does not automatically re-review a pull request after new pushes unless you have configured automatic reviews to include new pushes. If you rely on a one-time review and then change the branch, the earlier comments can become stale.

There is also a branch-context detail that matters. When Copilot reviews a pull request, it reads repository custom instructions, agent instructions, and agent skills from the head branch, not the base branch. If you change review guidance in the feature branch, Copilot uses that version for the review of that PR.

In practice, that means Copilot can help a team check work before a PR is opened, but only in the sense of an iterative branch workflow. It does not quietly inspect its own output and certify it as done. The review step still happens on the PR, and the branch still needs a human to decide whether the changes are ready to merge.

If you are using Copilot to cut down review time, the best use is to catch obvious correctness, readability, or maintainability problems before a person spends time on them. GitHub’s own guidance describes this as spending more human review time on design tradeoffs and product impact instead of obvious issues that could have been caught earlier.

For teams building on DevConnect, the same principle applies: keep the early feedback loop on work you control, then move to a human-readable pull request once the branch is clean. DevConnect itself is free to use, and you can use it alongside your normal review flow, but the review logic still lives in GitHub, not inside the app. https://devconnectplatform.com

So the short answer is yes, Copilot can review the changes it helped produce before you open or finalize a pull request, but only as part of a separate review step. It is a pre-PR branch workflow plus a PR review, not a single self-verifying agent pass.

FAQ

Can Copilot approve its own pull request No. GitHub says Copilot code review leaves comment reviews only. It does not produce an approval or a request-changes review, and it does not count toward required approvals.

Can I ask Copilot to fix what it just reviewed Yes. GitHub documents a “Fix with Copilot” flow from review comments, where Copilot can create a draft response, create a new pull request against the branch, or commit changes to the same pull request.

Does Copilot review changes before I open the pull request Copilot can help you inspect and iterate on a branch before you open the PR, but the formal code review workflow happens on the pull request itself. GitHub recommends reviewing the diff before opening the PR, then using PR review once the branch is ready.

Will Copilot re-review after I push more commits Not by default. GitHub says Copilot does not automatically re-review a pull request after new pushes unless automatic reviews are configured for new pushes.

Does Copilot use the instructions from the base branch or the feature branch Copilot uses the head branch, the branch with your changes, when it reviews the pull request. That includes repository custom instructions, agent instructions, and agent skills.