add-webcodecs-bug
por remotion-dev
Adicionar um bug de WebCodecs do navegador à página de documentação de bugs do WebCodecs do Remotion Mediabunny. Use quando for fornecida uma URL de problema do Chromium, WebKit ou Firefox que deva ser rastreada…
npx skills add https://github.com/remotion-dev/remotion --skill add-webcodecs-bugAdd WebCodecs Bug
Workflow
- Read
packages/docs/docs/mediabunny/webcodecs-bugs.mdxto understand the current table format. - Open the provided issue URL with the
browser:control-in-app-browserskill. - On the issue page, verify:
- issue title
- created or filed date
- reporter or filed-by identity
- current status and resolution state
- Map the browser tracker to the table fields:
- Product: Chromium issues are
Chrome, WebKit Bugzilla issues areSafari, Mozilla Bugzilla issues areFirefox. - Filed by: use the known handle from the task when the tracker only exposes a redacted email. Known reporter mappings:
musica-viva.deordp@...@musica-viva.de→@Vanilagy
- Fixed?: use
Yesonly for fixed or verified-fixed issues,Nofor open/new/assigned/unresolved issues, andWon't fixfor explicitly rejected or wontfix resolutions.
- Product: Chromium issues are
- Add one Markdown table row to
packages/docs/docs/mediabunny/webcodecs-bugs.mdx.
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.
Verification
After editing, inspect the diff and confirm the row has the right URL, product, filed-by value, and fixed state.