Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.
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.
Review the instructions the agent will receive before you install.
packages/docs/docs/mediabunny/webcodecs-bugs.mdx to understand the current table format.browser:control-in-app-browser skill.Chrome, WebKit Bugzilla issues are Safari, Mozilla Bugzilla issues are Firefox.musica-viva.de or dp@...@musica-viva.de → @VanilagyYes only for fixed or verified-fixed issues, No for open/new/assigned/unresolved issues, and Won't fix for explicitly rejected or wontfix resolutions.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.
After editing, inspect the diff and confirm the row has the right URL, product, filed-by value, and fixed state.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.