forge-debugger

What problem does it solve?

Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira/Confluence app that "stopped working". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word "Forge" but describe a Jira panel or Confluence macro acting up.

Core Features & Use Cases

• Structured diagnostic workflow — Step-by-step checklist to identify root causes quickly: version checks, lint, build verification, deploy status, and log analysis
• Common error pattern matching — Instant lookup table covering 15+ frequent Forge errors (blank UI, resolver not found, 403s, 410 Gone, handler path issues, and more)
• Autonomous execution — The agent runs diagnostic and fix commands directly, without asking permission or presenting copy-paste instructions
• API migration guidance — Handles v1 → v2 REST API migration for Confluence and Jira endpoints
• Token-efficient debugging — Prioritizes cheap checks first (lint, version) and stops at root cause to minimize context usage

Quick Start

Describe the Forge issue you are facing and let the debugger start the guided diagnostic flow immediately.