메뉴
Drafts a Jira bug report for an FXA issue. Gathers repro steps, expected vs actual behaviour, and affected surface, outputs a structured report, and optionally files the ticket via the Atlassian MCP. Returns the new FXA-N key when filed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | fxa-jira-bug-description |
| description | Drafts a Jira bug report for an FXA issue. Gathers repro steps, expected vs actual behaviour, and affected surface, outputs a structured report, and optionally files the ticket via the Atlassian MCP. Returns the new FXA-N key when filed. |
| user-invocable | true |
Draft a Jira bug report for an FXA issue, and optionally file the ticket via the Atlassian MCP. Do not create, edit, or suggest changes to any source files.
If a Sentry link, error log, or stack trace was provided, read it first and infer as much as possible before asking anything.
Required information:
Also useful — ask only for what is missing:
If all required information is clear, proceed directly to Step 2.
Search only the packages likely involved. Find:
git log on the relevant files)Incorporate findings directly into Root Cause and Key Reference Files. Surface genuine unknowns as Open Questions.
Summary: [area] <concise bug description> — e.g. [auth] Passkey registration fails silently when device has no authenticator
Background: What the bug is, where it occurs, and who is affected. 2–3 sentences.
Steps to Reproduce: Numbered steps from a known starting state. Include account state and environment where relevant.
Expected Behaviour: What should happen.
Actual Behaviour: What actually happens. Include error message, code, or Sentry event if available.
Affected Surface: Which users, flows, account states, browsers, or environments are affected. Note if intermittent.
Severity: (Critical / High / Medium / Low)
Root Cause: (if known or suspected — omit if unknown) Where in the code the bug originates. Reference specific file and function if identified.
Acceptance Criteria:
Key Reference Files: Specific files relevant to investigation or fix. One line each.
Out of Scope: (omit if not needed)
Open Questions: (omit if none)
After producing the draft (Step 3), check whether the Atlassian MCP is available in the current session (look for mcp__atlassian__createJiraIssue in the available tools). If not available, stop — the user files the ticket manually using the drafted description.
If available, ask the user via AskUserQuestion whether to file now:
If the user picks "Skip", stop and output the draft. If "File now", call mcp__atlassian__createJiraIssue with:
cloudId: mozilla-hub.atlassian.net (the Atlassian MCP accepts the site hostname directly; fall back to getAccessibleAtlassianResources if the call ever rejects this form).projectKey: FXAissueTypeName: Bugsummary: the [area] <concise bug description> line from Step 3description: the rest of the drafted body from Step 3 (Background, Steps to Reproduce, Expected/Actual, Severity, etc.)contentFormat: markdownSurface the returned FXA-N key and the issue URL. That key is this skill's return value when invoked inline by another skill (e.g. /fxa-pr-open uses it to populate the Closes: line).
Generates a two-audience changelog from merged PRs in the FxA monorepo: a plain-language product summary and an engineer handoff with operational notes. Name a train (e.g. "341") or pass any git range; with no argument it defaults to the in-development train on main (the latest release tag up to HEAD — not a deployed stage/prod train), framed as the range the train owner is accountable for. Use for train-owner handoffs, train summaries, or "what shipped" questions.
Generates a daily FxA triage summary. Queries Jira, GitHub, Bugzilla, and optionally Sentry, then outputs a Slack-ready update with detailed analysis. Use when starting triage duties or preparing the daily triage post.
Simplifies and refines code in the FXA monorepo using project-specific conventions. Use when asked to simplify, clean up, or refine recently written code. Focuses on recently modified code unless instructed otherwise.
Reviews changed React/TSX code for component design, hooks misuse, performance, accessibility, and state management issues. Reports findings with severity and concrete fix recommendations. Operates on files changed vs main.
Fast single-pass FXA-specific commit review covering security, conventions, logic/bugs, tests, and migrations. No subagents — runs directly in the main context.
Thorough FXA-specific commit review using parallel specialist agents. Covers security, TypeScript, logic/bugs, test quality, and architecture. Agents explore call sites, git history, and monorepo conventions.