add-webcodecs-bug

Add browser WebCodecs bug entries to the Remotion Mediabunny documentation table.

57.9k|4.4k|Updated Jun 23, 2020
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill add-webcodecs-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-webcodecs-bug
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/add-webcodecs-bug
Command: npx skills add https://github.com/remotion-dev/remotion --skill add-webcodecs-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracking browser-specific WebCodecs bugs across Chromium, WebKit, and Firefox requires manually visiting each issue tracker, extracting metadata, and formatting it consistently into the Remotion Mediabunny documentation. This Skill automates that lookup and table-update workflow.

Core Features & Use Cases

  • Issue Metadata Extraction: Reads issue title, filing date, reporter, and resolution state from Chromium, WebKit Bugzilla, and Mozilla Bugzilla trackers.
  • Browser Mapping: Translates tracker sources into the correct product label (Chrome, Safari, Firefox) and applies known reporter handle mappings.
  • MDX Table Update: Appends a properly formatted Markdown table row to packages/docs/docs/mediabunny/webcodecs-bugs.mdx while preserving existing columns.
  • Use Case: A maintainer receives a Chromium issue URL about a WebCodecs decoding failure. Use this Skill to fetch the issue details, map the reporter, determine the fixed state, and add the row to the public bugs documentation.

Quick Start

Add the WebCodecs bug from this Chromium issue URL to the Mediabunny webcodecs-bugs documentation page.

Frequently Asked Questions about add-webcodecs-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a WebCodecs bug to Remotion Mediabunny docs?

Provide the browser issue URL and the skill reads the existing MDX table format, fetches the issue title, date, reporter, and status, then appends a new row to packages/docs/docs/mediabunny/webcodecs-bugs.mdx.

What issue trackers does the WebCodecs bugs skill support?

The skill supports Chromium issues, WebKit Bugzilla entries, and Mozilla Bugzilla reports. Each tracker maps to a product label: Chrome, Safari, or Firefox respectively.

How does the skill handle redacted reporter emails?

When a tracker only exposes a redacted email, the skill applies known handle mappings such as musica-viva.de or dp@[email protected] resolving to @Vanilagy.

What fixed-state values are used in the bugs table?

The skill uses Yes for fixed or verified-fixed issues, No for open, new, assigned, or unresolved issues, and Won't fix for explicitly rejected or wontfix resolutions.

Can the skill add a date column to the bugs table?

No, the skill preserves existing table columns and wording. It only adds a date column if the docs file already has one or the user explicitly requests it.