// Launch a local web server and open a browser page listing all bug triage reports in ./reports, with live JS text filtering.
| 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.
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).
Firefox bug triage assistant for media, web conferencing, and graphics related issues.
Generate technical documentation for a specified technology domain with optional customization.
Generate or modify Firefox mozconfig build configuration files. Use when the user asks to create a mozconfig, configure a build, set up ASan/TSan/debug builds, or match try server configurations.
Firefox bug triage assistant for determining if a bug severity rating of S1 or S2 is warranted, and to gather information for triaging and prioritization.