uplift-request

Draft Firefox uplift approval requests for Beta, Release, and ESR bugs.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mozilla/media-skills --skill uplift-request
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uplift-request
Source: https://github.com/mozilla/media-skills/tree/main/uplift-request
Command: npx skills add https://github.com/mozilla/media-skills --skill uplift-request

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of preparing Firefox uplift approval requests, so you can move a finished fix onto Beta, Release, or ESR with the right context and fewer mistakes.

Core Features & Use Cases

  • Bug and patch intake: Locates the relevant bug, local commits, and attachment state before drafting the request.
  • Security-aware handling: Runs a one-time sanitization audit for sec-* bugs and keeps sensitive details out of later steps.
  • Channel-specific drafting: Builds the nine-question uplift form for Beta, Release, and ESR, grouping channels that share the same patch.
  • Submission support: Helps with either Phabricator-based uplift flow or raw-patch Bugzilla flagging when needed.

Quick Start

Ask the uplift-request skill to prepare the Firefox uplift approval comment for a given bug ID and target channels.

Frequently Asked Questions about uplift-request

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

FAQPage Schema
How do I draft a Firefox uplift approval request for Beta, Release, or ESR?

Drafting a Firefox uplift approval request involves locating the relevant bug, inspecting local patches or Bugzilla attachments, and generating the nine-question uplift form for your target release channels. The process groups channels sharing the same patch to streamline submission.

What is the process for uplifting a security regression to a Firefox release channel?

Uplifting a security regression requires running a one-time sanitization audit for sec-* bugs to keep sensitive details out of later steps. The process then builds the channel-specific uplift questionnaire while ensuring sensitive data is properly sanitized.

Do I need a Bugzilla API key to prepare Firefox uplift approvals?

Preparing Firefox uplift approvals requires Bugzilla API-key checks to access bug data and attachment states. You also need release-calendar version lookup to identify the correct target train versions for Beta, Release, or ESR channels.

Can I use Phabricator to submit Firefox uplift requests?

Submitting Firefox uplift requests supports either Phabricator-based uplift flow via moz-phab or raw-patch Bugzilla flagging when needed. The process handles attachment matching and local diff inspection to prepare the correct submission format.

What's the best way to handle channel selection when requesting a Firefox uplift?

Channel selection for Firefox uplift requests involves grouping channels that share the same patch and drafting separate questionnaires for Beta, Release, and ESR. This ensures the correct release train versions are targeted based on release-calendar lookup.