forge-debugger

Diagnose and fix Atlassian Forge app issues across Jira and Confluence.

20|10|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/atlassian/forge-skills --skill forge-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-debugger
Source: https://github.com/atlassian/forge-skills/tree/main/skills/forge-debugger
Command: npx skills add https://github.com/atlassian/forge-skills --skill forge-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about forge-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a blank Custom UI panel in my Atlassian Forge app?

To fix a blank Custom UI panel in a Forge app, run a structured diagnostic workflow that checks linting, build verification, and deploy status. The debugger matches common error patterns like missing resolvers to execute fixes autonomously.

Why does my Forge app show a 403 error or fail to appear after installation?

A Forge app shows a 403 error or fails to appear after installation due to missing scopes or permission problems. The debugger analyzes forge logs and deploy status to pinpoint the permission gap and applies the required fixes immediately.

Can I debug Jira or Confluence integrations if the Forge CLI cannot be installed?

You can debug Jira or Confluence integrations without the Forge CLI by using an npx fallback. The debugger autonomously runs diagnostic commands through this fallback to investigate runtime failures and deploy-time errors.

What is the best way to troubleshoot Forge resolver errors and handler path issues?

The best way to troubleshoot Forge resolver errors and handler path issues is using an autonomous step-by-step diagnostic checklist. It prioritizes cheap checks like version verification and linting before analyzing logs to minimize context usage.

How do I migrate Confluence and Jira REST API endpoints from v1 to v2?

To migrate Confluence and Jira REST API endpoints from v1 to v2, use the API migration guidance provided during the debugging workflow. This addresses unexpected output and production vs dev discrepancies by updating endpoint calls directly.