gramax

Use when user wants to inspect Bugsnag errors for Gramax (top events, frequent crashes, impact ranking, error detail, mark fixed). Triggers on "bugsnag", "багснаг", "top errors", "most frequent crashes", "что в багснеге", "посмотри багснаг", "fix bug in bugsnag", "resolve error", "mark fixed", "examine error", "show error". Two Bugsnag projects exist: **Gramax-PROD** and **Gramax-DEV**. Pass full project name via `--project <name>`. Splits results by platform (TAURI/NEXT/BROWSER/...) parsed from message prefix. Includes stacktrace + full event metadata. Outputs JSON. Before patching code, invoke the `superpowers:systematic-debugging` skill — feed it the `show --error <id>` output. **Marking an error fixed in Bugsnag is not the actual fix** — the code change must reach the latest release branch via either (1) a GitLab MR targeting the latest `release/*` branch, or (2) a commit on `develop` followed by a cherry-pick to the latest `release/*` branch. Use `fix` only after the change is merged/cherry-picked.

Use when user asks to triage, process, or label GitHub issues in the Gramax project. Triggers on: "обработай заявки", "разбери ишью", "обработай ишью", "расставь лейблы", "needs-triage", specific issue numbers like "#1234". Also triggers when user mentions issues are missing impact, subsystem, or priority.

Use when user asks to write, create, run, or debug Playwright e2e tests in the Gramax project. Triggers on keywords like e2e, playwright, test, spec, QA.