add-webcodecs-bug
npx mdskill add remotion-dev/remotion/add-webcodecs-bug1. Read `packages/docs/docs/mediabunny/webcodecs-bugs.mdx` to understand the current table format. 2. Open the provided issue URL with the `browser:control-in-app-browser` skill. 3. On the issue page, verify: - issue title - created or filed date - reporter or filed-by identity - current status and resolution state 4. Map the browser tracker to the table fields: - Product: Chromium issues are `Chrome`, WebKit Bugzilla issues are `Safari`, Mozilla Bugzilla issues are `Firefox`. - Filed by: use the known handle from the task when the tracker only exposes a redacted email. - 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. 5. Add one Markdown table row to `packages/docs/docs/mediabunny/webcodecs-bugs.mdx`.
--- name: add-webcodecs-bug description: Add 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, reporter, and resolution state before editing the MDX table. --- # Add WebCodecs Bug ## Workflow 1. Read `packages/docs/docs/mediabunny/webcodecs-bugs.mdx` to understand the current table format. 2. Open the provided issue URL with the `browser:control-in-app-browser` skill. 3. On the issue page, verify: - issue title - created or filed date - reporter or filed-by identity - current status and resolution state 4. Map the browser tracker to the table fields: - Product: Chromium issues are `Chrome`, WebKit Bugzilla issues are `Safari`, Mozilla Bugzilla issues are `Firefox`. - Filed by: use the known handle from the task when the tracker only exposes a redacted email. - 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. 5. 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.
- add-cli-optionAdd a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.
- add-effectAdd a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, tests, formatting, and builds.
- add-expertAdd a new expert to the Remotion experts page
- add-new-packageAdd a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, tests, and release checklist updates. Use when creating a new @remotion package.
- add-sfxAdd a new sound effect to @remotion/sfx
- docs-demoAdd an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
- fix-dependabotFix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing
- flakeTrack Remotion CI flakes in issue #8375, increment repeated signatures, discover failed PR checks when no PR is given, and rerun flaky GitHub Actions jobs.
- issueCreate or update GitHub issues with correct Remotion naming and safe multiline Markdown handling
- issue-managementManage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.