update-media-lib

Automate vendored Firefox media library updates via mach vendor and patches.

Updated Mar 14, 2016
One-click install
npx skills add https://github.com/ChunMinChang/dotfiles --skill update-media-lib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-media-lib
Source: https://github.com/ChunMinChang/dotfiles/tree/main/mozilla/firefox/dot.claude/skills/update-media-lib
Command: npx skills add https://github.com/ChunMinChang/dotfiles --skill update-media-lib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the maintenance of Firefox's vendored media libraries by coordinating updates to libvpx, libdav1d, libaom, libopus, libcubeb, libwebp, libjxl, and related components within the Firefox source tree. It reduces manual drift between upstream releases and the Mozilla build system.

Core Features & Use Cases

  • Automated library identification and vendor workflow: Reads moz.yaml configurations to determine update paths for each library.
  • Flexible update strategies: Supports two-step with patches, simple vendor updates, and script-based updates depending on the library.
  • Process guidance and auditing: Provides a repeatable process including Review, patch application, build/test, and optional cargo vet audits for Rust crates.

Quick Start

Run the skill to begin vendor updates for Firefox media libraries, then follow prompts to choose libraries and update modes.

Frequently Asked Questions about update-media-lib

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

FAQPage Schema
How do I update vendored media libraries in Firefox?

Updating vendored media libraries in Firefox involves identifying the library, consulting its moz.yaml configuration, running mach vendor, applying patches when required, and testing the build. This skill automates that workflow for libvpx, libdav1d, libaom, libopus, libwebp, libjxl, and other media components, handling library-specific vendor methods and patch application.

What are the different vendor update strategies for Firefox media libraries?

Firefox media libraries support three vendor update strategies: two-step updates with patches for complex libraries, simple vendor updates for straightforward upgrades, and script-based updates for specialized components. The moz.yaml configuration guides which strategy applies to each library.

Do I need to manually apply patches when updating Firefox's vendored libraries?

Patch application depends on the library's vendor method defined in moz.yaml. Some libraries require manual or automated patch application after vendoring; others use simple vendor workflows without patches. This skill follows per-library guidance and applies patches when needed.

How do I audit Rust crates after updating vendored libraries?

After updating vendored Rust crates, you can optionally run cargo vet audits to validate dependencies. This skill supports the cargo vet audit step as part of its standardized workflow for Rust media components.

What happens after I vendor an updated media library in Firefox?

After vendoring, the workflow includes building and testing the Firefox source tree to ensure the updated library integrates correctly. For Rust crates, optional cargo vet audits validate the dependencies before final integration.