Have Copilot plan, patch, and open the PR for you

A developer used GitHub Copilot to shape a ticket into a plan, make the edits, and prepare the ticket and pull request after a manual check.

Done with GitHub Copilotยท Intermediateยท Oct 2026

What they did
They built the workflow in two stages. First, one skill took a Jira issue and turned it into an action list; then a second skill used that list to apply the code changes. The agent printed the proposed changes, stopped for approval, and only then moved ahead to update the ticket, create the pull request, and refresh the PR text. Another user said they mostly use GitHub Copilot for GitHub-side work such as reviewing code, adding PR notes, and handling repository chores.
How it went
The thread focused on process rather than measurable gains. The main user said they still keep a human gate before pushing and are not ready to let it run fully on its own; they also said they do not really enjoy this setup.
Tips
If the agent can affect a branch, ticket, or PR, make it stop and ask before anything is sent. A good test prompt should ask for the plan first, then the changes, then a final approval step before publish actions.

Try it yourself with GitHub Copilot

In [repo], take [ticket link or ID] and convert it into a short implementation plan. Use that plan to make the code changes, then show me the diff along with a draft ticket update and pull request title/description. Do not push, submit, update, or open anything until I approve the proposed changes. After the pull request exists, inspect it for spots that may need review comments and list them for me.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.