I know Iโm a bit late to the party โ but I finally finished the first Forge Quest.
Since Iโve been working with Forge for quite a while, I set myself a special challenge:
๐ Donโt write any code myself.
Instead, I let the Rovo Dev Agent in the Atlassian CLI do all the heavy lifting.
You might think: โBut this isnโt the Atlassian Developer Communityโฆโ
And youโre right.
Still, I believe admins and managers should also know about the advantages of using AI-powered tools for coding. Because the possibilities go far beyond โjust writing code.โ
Here are my key learnings ๐
๐ฌ Explanations: The agent explained every step it took and even suggested next actions.
โ Permissions: It explicitly asked for approval before writing code.
๐ CLI integration: Forge CLI was included seamlessly.
๐ ๏ธ Flexibility: I could still use git and other terminal commands in parallel.
๐ Scopes: When I added Jira API calls, the agent automatically updated the manifest with the required scopes.
๐ค Code improvements: It suggested meaningful improvements โ and combining this with the Rovo PR Reviewer was a great match.
๐ Sometimes the agent did more than I asked for, e.g. extending commit messages or adding unnecessary code. But it was able to roll back changes once asked for.
๐ Some info was outdated โ for example, it insisted that UI Kit canโt call Jira APIs, which is no longer true. But after a while I convinced it
I know these were relatively simple tasks that I could have written faster by hand. But the fact that the Dev Agent handled them so smoothly is impressive.
Next, I want to try this approach on more complex requirements and see how far it can go.
(By the way, I used the ChatGPT 5 model for this experiment.)
Have you tried the Atlassian CLI with Rovo Dev Agents yet?
Whatโs your experience โ and what use cases would you like to see supported?
Letโs exchange stories!
Paul Pasler _Seibert_
2 comments