One instrument. One useful task.
Turn an issue into a reviewed pull request
Step 1: An issue becomes a decree
An agent can use configured tools to read an issue, implement its criteria and prepare a pull request after review.
Still frames · every step is available
“Turn an issue into a reviewed pull request.”
An agent can use configured tools to read an issue, implement its criteria and prepare a pull request after review.
See who does what
Choose the task, workspace and permitted scope.
An agent can use configured tools to read an issue, implement its criteria and prepare a pull request after review. Start here: Connected issue → implementation → checks → configured PR tool.
Issue context, checks and proposed PR scope agree.
Issue access and PR creation use configured tools and their permissions.
Copy an example instruction
Illustrative task shared across these lessons. Adapt the scope and file ownership to your project. Try the complete example and inspect its tests →
Add a saved-filter control. Keep the change focused. Inspect the existing filtering behaviour, implement the control, and run the relevant checks. Ask a separate agent to review the diff without editing it. Collect its findings and resolve confirmed issues before proposing a commit.
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.
Illustrated explanation · The scene explains the workflow. Follow the guide to perform it in the app.
About this demonstration
Instructions reviewed against product 1.5.119. Authored illustration; no application execution is claimed.