Take an issue to a pull request
On this page
Bring an issue's context into an agent session, implement the change and prepare a reviewable branch.
Before you start
Open the correct repository workspace. Configure Jira if the task comes from Jira. For GitHub pull requests and CI, provide an authenticated GitHub CLI (gh) on the execution machine or a compatible connected tool with the required repository access.
The exact hosted actions depend on that CLI or tool. A connection does not imply that every tracker has a native board in Code Overlord.
Work through the issue
- Give the agent an exact issue key or URL and ask it to read the description and acceptance criteria.
- Have it identify the target repository and the files likely to change.
- Create or choose an appropriate feature branch using the Git controls or an explicit agent instruction.
- Ask it to implement the task and run the relevant checks.
- Ask the agent to show the Git diff and test results in its terminal. Request a second-agent review when useful.
- Commit the approved changes, then explicitly ask the agent to push the branch and create a draft PR through the configured GitHub tool or CLI.
- Ask it to inspect the PR checks and return the PR link with the result.
Example instruction
Replace the sample key with an issue you can access:
Read APP-123 from Jira. Summarise its acceptance criteria, implement the scoped fix on a feature branch and run the relevant tests. Leave the changes ready for my review.
After review:
Commit the reviewed changes, push this feature branch and create a draft GitHub pull request. Include the issue reference and test results. Check CI and return the PR URL.
Use another tracker
Add a compatible MCP server through Connect business tools and MCP. Ask the agent to list the available read/update actions before relying on them. Linear's native Orca board is not a documented Code Overlord control; a configured integration is the route here.
Check the result
Open the returned PR. Verify the repository, base branch, diff, issue reference and checks. A local commit is not evidence that a PR was created successfully.