fxa-pr-open

Drafts and opens FXA pull requests as drafts following the repo PR template and team conventions.

685|236|Updated Jun 3, 2015
One-click install
npx skills add https://github.com/mozilla/fxa --skill fxa-pr-open
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fxa-pr-open
Source: https://github.com/mozilla/fxa/tree/main/.claude/skills/fxa-pr-open
Command: npx skills add https://github.com/mozilla/fxa --skill fxa-pr-open

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Opening a pull request in the Mozilla Accounts (fxa) monorepo involves strict conventions: Jira ticket alignment, a specific PR template, draft-only creation, and manual checklist attestations. This Skill automates the drafting and opening workflow while enforcing every team rule so nothing is missed.

Core Features & Use Cases

  • Alignment pass before drafting: Compares the Jira ticket, commit messages, and diff scope to surface scope creep, uncovered acceptance criteria, and commit-type inconsistencies before any PR text is written.
  • Template-faithful drafting: Reads .github/PULL_REQUEST_TEMPLATE.md and fills in Because/This pull request/How to review sections following title and body conventions (type(scope): subject, Closes: FXA-N).
  • Safe state changes: Pushes the branch and opens the PR as a draft via gh pr create --draft only after explicit user confirmation, never force-pushing or touching existing PRs.
  • Use Case: You finished a feature branch for FXA-13099 touching fxa-settings. The skill fetches the ticket, checks your commits against the acceptance criteria, asks about reviews and screenshots, drafts the PR body, and opens it as a draft after your approval.

Quick Start

Ask the assistant to open an FXA pull request for the current branch, optionally providing a Jira key like FXA-13099.

Frequently Asked Questions about fxa-pr-open

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

FAQPage Schema
How do I open a draft pull request for the fxa repository?

Run this skill on a pushed or unpushed feature branch. It fetches origin/main, gathers commits and diff scope, aligns them with the Jira ticket, drafts the title and body from the repo PR template, and opens the PR with gh pr create --draft after your explicit approval.

How does the skill align commits with a Jira ticket?

It extracts the FXA-N key from the branch name or arguments, fetches the ticket summary and acceptance criteria via the Atlassian MCP, then compares them against commit messages and the changed-file diff to flag scope mismatches or uncovered acceptance criteria.

Can this skill edit or update an existing pull request?

No. The skill is strictly for opening new PRs. If gh pr view shows a PR already exists for the branch, it stops and asks how to proceed; editing an existing PR is a separate workflow requiring its own confirmations.

Why does the skill refuse to check the PR template checklist boxes?

The checklist items are manual attestations (GPG signing, tests run locally, docs, RTL verification, AI code review) that only the user can truthfully confirm. Team policy forbids the skill from ticking them on the user's behalf.

What happens if my branch has no Jira ticket?

The skill offers to create a feature or bug ticket via the fxa-jira authoring skills, lets you provide an existing key, or allows a waiver for chore-only work with the Closes line set to N/A.