About add-webcodecs-bug
A skill for documenting WebCodecs bugs in Mediabunny’s documentation. It verifies issue details, maps tracker data to the existing table fields, and checks the resulting change.
Key features
- 01Review the existing bug table format
- 02Verify issue details in the browser
- 03Map tracker data to table fields
- 04Add and inspect a Markdown row
Use cases
- 01Record a newly reported WebCodecs bug
- 02Update bug status from a browser issue page
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ remotion-dev/ remotion --skill add-webcodecs-bugAfter installing, type/add-webcodecs-bugin Claude Code to confirm it loaded.
Details
From the project READMEAdd 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@[email protected]→@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.
Comments
Markdown supported