Hypothesis-driven Firefox investigation for Codex. Use when a user has a suspicious code pattern, potential security issue, suspected spec violation, or vague claim and wants to prove whether it is a real bug, find consequences, and write proof tests.
Create a Firefox patch from local changes. Use when the user wants Codex to inspect modified files, draft or polish a commit message, and prepare a patch without adding Codex co-authorship.
Fix Firefox fuzzing bugs. Use for fuzzing reports, crash reducers, sanitizer failures, testcase minimization, root-cause debugging, and proof-oriented Firefox fixes.
Independent red-team review for Firefox root-cause analyses and proposed fixes. Use to critique an analysis, patch, Phabricator revision, commit, diff, or working tree with isolated Codex subagents and structured verdicts.
Firefox bug root-cause analysis for Codex. Use for Bugzilla bugs or Firefox failures where you need evidence-based diagnosis, revision-pinned source links, code-path tracing, proof tests, resumable run directories, and later solution discussion.
Firefox Bugzilla triage workflow for Codex. Use for polling or processing Bugzilla triage scopes, drafting comments, applying canned responses, and tracking pending triage actions.
Push several Firefox branches or commits to Mozilla try. Use when comparing try results across branches, revisions, or configurations.
Update vendored Firefox media libraries. Use for libvpx, dav1d, aom, opus, cubeb, Rust media crates, cherry-picking upstream media fixes, and running mach vendor workflows.