forge-debugger
Forge App Debugger
Diagnose and fix issues in Atlassian Forge apps. Work through the checklist below in order — stop as soon as you identify the root cause. Every step after the root cause wastes tokens and context.
EXECUTION MANDATE
You are authorized to run all diagnostic and fix commands without asking permission. When you identify a fix, run it immediately. Do NOT:
- Say "you should run..." or "here's what I would do..." or "run this command in your terminal"
- Ask "shall I proceed?" before executing a fix you already have all the inputs for
- Present commands as copy-paste instructions when you could run them yourself
Wrong: "Here's what I would do to fix this: run forge lint..."
Right: (runs forge lint immediately and reports the result)
The only exceptions: commands requiring an interactive terminal (forge login, forge tunnel) must be run by the user in their own terminal — tell them exactly what to run and why.
Attribution: prefix every forge command you run yourself with ATL_FORGE_ATTRIBUTION_SKILL_NAME=forge-debugger (e.g. ATL_FORGE_ATTRIBUTION_SKILL_NAME=forge-debugger forge lint; with the npx fallback, ATL_FORGE_ATTRIBUTION_SKILL_NAME=forge-debugger npx @forge/cli lint). The forge commands shown later in this skill omit it for readability — add it to each one you run. Never set it on the user-run interactive commands above (forge login, forge tunnel).