$npx -y skills add remotion-dev/remotion --skill add-webcodecs-bugAdd a browser WebCodecs bug to the Remotion Mediabunny WebCodecs bugs docs page. Use when given a Chromium, WebKit, or Firefox issue URL that should be tracked in packages/docs/docs/mediabunny/webcodecs-bugs.mdx, especially when needing to look up the issue title, filing date, re
| 1 | # Add WebCodecs Bug |
| 2 | |
| 3 | ## Workflow |
| 4 | |
| 5 | 1. Read `packages/docs/docs/mediabunny/webcodecs-bugs.mdx` to understand the current table format. |
| 6 | 2. Open the provided issue URL with the `browser:control-in-app-browser` skill. |
| 7 | 3. On the issue page, verify: |
| 8 | - issue title |
| 9 | - created or filed date |
| 10 | - reporter or filed-by identity |
| 11 | - current status and resolution state |
| 12 | 4. Map the browser tracker to the table fields: |
| 13 | - Product: Chromium issues are `Chrome`, WebKit Bugzilla issues are `Safari`, Mozilla Bugzilla issues are `Firefox`. |
| 14 | - Filed by: use the known handle from the task when the tracker only exposes a redacted email. Known reporter mappings: |
| 15 | - `musica-viva.de` or `dp@...@musica-viva.de` → `@Vanilagy` |
| 16 | - Fixed?: use `Yes` only for fixed or verified-fixed issues, `No` for open/new/assigned/unresolved issues, and `Won't fix` for explicitly rejected or wontfix resolutions. |
| 17 | 5. Add one Markdown table row to `packages/docs/docs/mediabunny/webcodecs-bugs.mdx`. |
| 18 | |
| 19 | Preserve the existing table columns and wording. Do not add a date column unless the docs file already has one or the user explicitly asks for it. |
| 20 | |
| 21 | ## Verification |
| 22 | |
| 23 | After editing, inspect the diff and confirm the row has the right URL, product, filed-by value, and fixed state. |