StepGleam logoStepGleam
Coding guide

Hand a well-scoped issue to GitHub Copilot's cloud agent and review its PR

Write the issue like a ticket for a junior engineer, assign it to Copilot, steer it with @copilot comments on the PR, and review it like any other contribution.

~25 minBeginner 78/100 5 steps Updated Oct 26, 2026
GitHub Copilot cloud agentGitHub
Hand a well-scoped issue to GitHub Copilot's cloud agent and review its PR — illustration for this Coding guide

Tools used

Step navigator0/5 done
0 of 5 steps done
What you'll get

A merged Copilot PR that you reviewed and iterated on, with a second approver if your repo requires one.

Who this is for

Teams and solo developers with a backlog of small, clear issues.

Read this first

Before you start

Developers on r/GithubCopilot and r/github who assign issues to Copilot describe the same arc: vague issues fail, detailed ones work, and you iterate through PR comments. GitHub's docs add the review rules.

Step-by-step instructions

Step 1 of 5 · Coding

Pick an issue you would give a junior-to-mid engineer

One heavy user's test: "Is this an issue that I would assign to a junior-mid level software engineer?" They break large projects into smaller tickets and assign them one at a time. Triage, they found, doesn't work well.

Hand a well-scoped issue to GitHub Copilot's cloud agent and review its PR — guide thumbnail
Step 2 of 5 · Coding

Write the issue in more detail than feels necessary

"It took a few attempts to understand that issues have to be overly descriptive and detailed. Once the issue had better instructions, copilot managed to successfully complete a legit pending issue from our backlog." Another user says it works on "any issue that has good custom instructions or agent md file steering the agent."

Step 3 of 5 · Coding

Assign the issue to Copilot

Assign the issue to Copilot. It creates a branch and a PR, works in GitHub Actions, and asks for your review when done. One user notes it always branches from the default branch, even if you name another.

Step 4 of 5 · Coding

Steer it with @copilot comments on the PR

To request changes, mention @copilot in a PR comment or push commits to the branch. A user: "you can keep adding comments to the pull request and copilot will continue working based on your comments."

Copy-ready promptGitHub
@copilot the date filter should include the end date; add a test for that case.
Step 5 of 5 · Coding

Review it like any contribution and check workflow changes

GitHub's docs say Copilot PRs "deserve the same thorough review as any contribution." Actions don't run automatically on Copilot's pushes, so read the diff first, especially anything in .github/workflows/. If approvals are required, your approval doesn't count toward them; another reviewer must approve.

Why this works

Workflows can access secrets.

End of guide · Reviewed Oct 26, 2026

Pro tips2
  • Add repository instructions such as AGENTS.md so every task starts with your conventions.
  • Keep tickets small: one concern per issue.
Common mistakes2
  • Assigning a one-line issue and expecting the right result.
  • Approving workflow runs without reading changes to .github/workflows.
FAQ2
Does it run tests?
Users report it iterates in GitHub Actions and usually finishes with passing tests, though not always.
Which plans have it?
GitHub lists the cloud agent for all paid Copilot plans.