메뉴
Launch a local web server and open a browser page listing all bug triage reports in ./reports, with live JS text filtering.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
File a Bugzilla bug directly via the BMO REST API with full power the prefilled enter_bug.cgi form can't do — create the bug AND upload one or more attachments (logs, patches, testcases, screenshots) AND set bug-/attachment-level flags (needinfo?, review?, sec-approval?, approval-mozilla-*?, tracking flags) in one confirmed operation. Also attaches files to, and sets flags on, existing bugs. Use when the user wants to actually submit a bug (not just open a draft form), attach files while filing, or set flags. For a simple file-it-myself-in-the-browser draft with no attachments, prefer the form-based `bug-filing` skill instead. Requires a Bugzilla API key.
Help prepare a Firefox security approval request by analyzing local commits/changes and drafting answers to the sec-approval questionnaire. Use when setting sec-approval? on a Bugzilla bug.
Help prepare a Firefox uplift approval request (Beta, Release, and/or ESR) by checking whether patches are already on the bug, auditing sanitization once for sec-* bugs, and drafting the approval comment per https://wiki.mozilla.org/Release_Management/Uplift_rules. Use after a fix is ready and needs to ride into a stabilization branch. May or may not follow sec-approval (sec-moderate typically skips sec-approval but may still need uplift).
Reference for constructing revision-pinned source, spec, and bug permalinks (Searchfox, GitHub, GitLab, googlesource, Codeberg, Chromium, FFmpeg, Bugzilla, specs). Use when citing code, specs, or bugs in analysis or reports and you need stable, revision-pinned URLs instead of trunk/HEAD links.
Firefox bug triage assistant for media, web conferencing, and graphics related issues.
Generate technical documentation for a specified technology domain with optional customization.
| name | list-reports |
| description | Launch a local web server and open a browser page listing all bug triage reports in ./reports, with live JS text filtering. |
Launch a local python web server that displays media-bug-triage reports from your ./reports/ folder, in a filterable and sortable browser UI.
Individual rows, each dedicated to summaryzing one report - In each row, display entries with the following information from the report:
| What | Color | Notes |
|---|---|---|
| Bug ID | Green | format: 'Bug NNNNN', linked to the bug in Bugzilla |
| Report generated date | Gray | Date when the report was generated |
| Component | Red | The component to which the bug belongs |
| Severity/Priority | Gray | The severity and priority of the bug |
| Reporter | Black | The user who reported the bug |
Additionally, the browser fetches the following live properties from Bugzilla asynchronously after the page loads, and updates each row as results arrive:
| What | Color | Notes |
|---|---|---|
| Status | Green unless RESOLVED, then Black. | The current status of the bug |
| Severity | Red if S1/S2, Green otherwise | The current severity of the bug |
| Priority | Red if P1/P2, Green otherwise | The current priority of the bug |
Finally, display the report's research summary text, up to 500 characters.
Run the following command from the repository root:
python3 .claude/skills/list-reports/server.py
The script picks a free port automatically and opens the browser. Tell the user:
Do not do anything else. Just run the command.
| Endpoint | Purpose |
|---|---|
GET https://bugzilla.mozilla.org/rest/bug/{id}?include_fields=id,summary,status | Fetch id,summary, and status |
GET https://bugzilla.mozilla.org/rest/bug/{id} | Fetch all bug fields |
GET https://bugzilla.mozilla.org/rest/bug/{id}/comment | Fetch all comments |
GET https://bugzilla.mozilla.org/rest/bug/{id}/history | Fetch change history |
GET https://bugzilla.mozilla.org/rest/bug/{id}/attachment | Fetch attachment metadata |
GET https://bugzilla.mozilla.org/rest/bug?product=...&component=...&creation_time=...&summary=... | Search bugs |
Use the include_fields query parameter to limit response size when only a subset of fields is needed.