Gekko2

🦎 Meet Gekko: The AI Race Engineer for Your Pull Requests

"Context switching is the enemy of velocity."

Every developer knows the pain: You push code, update Jira, and then... you wait. You tab-switch to Bitbucket to check the build. You tab-switch to Slack to nudge a reviewer. You tab-switch back to Jira.

This "polling loop" destroys flow state. It’s like an F1 driver stopping mid-race to check their own tire pressure.

For Codegeist 2025, we built Gekko—an AI-powered "Race Engineer" that lives inside Jira and brings live code telemetry directly to you.

🚀 What Gekko Does

Instead of hunting for status updates, Gekko brings them to your Jira ticket via Rovo Chat:

• The PR Stalker: Ask "Status?" and Gekko instantly fetches live data from Bitbucket. It doesn't just say "Open"—it tells you "2/3 Approvals, but Alice requested changes to auth.js."
• Build Telemetry: No more refreshing CI/CD pipelines. Gekko tells you if your build failed, when, and why.
• The Blocker Whisperer: Gekko reads through dozens of comments and highlights only the actionable blockers, filtering out the noise.

🛠️ How We Built It (The Tech Stack)

We leveraged the Model Context Protocol (MCP) architecture on Atlassian Forge:

1. The Brain: A Rovo Agent grounded in live data.
2. The Hands: Forge Serverless Functions that query the Bitbucket & Jira APIs in real-time.
3. The Result: A zero-context-switching experience. The AI doesn't hallucinate; it reports facts from your repo.

🔮 What’s Next?

We are moving from passive monitoring to active repairs. Imagine asking Gekko to "Rerun the failed pipeline" or "Merge this PR" without ever leaving Jira.

Gekko isn't just a tool; it's your pit crew. 🏎️💨

Built With

• forgecli