dotfiles

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.

Vendor a local Rust crate repository into Firefox for testing. Use when a user has local crate changes and wants them copied or converted into Firefox third_party/rust vendoring.

Root cause analysis for Firefox bugs with evidence-based code tracing, permanent source links, and proof tests. Two phases: diagnose, then discuss solutions.

Hypothesis-driven Firefox investigation: given a freeform suspicion that some code is buggy, unsafe, mis-behaving, or non-spec, blindspot validates the claim, finds real user-facing or security consequences (or proves there are none), and writes a bug-style report with revision-pinned code traces, original design intention from git history, and end-to-end proof tests. Triggers on: "/blindspot", "investigate this claim", "is this a real bug", "prove this is a bug", "find issues in <code>", "is this code safe", "what could go wrong with <code>".

Firefox bug triage assistant — fetches a Bugzilla bug via MCP, classifies signals, scopes searches to a media/web-conferencing/graphics/android profile, drafts a response, optionally generates a test page, and stages a pending draft you can apply to BMO via REST.

RedPen — independent review of a proposed root-cause-analysis solution. Spawns an isolated reviewer with no shared memory; returns a structured review doc with verdict, alternatives, and concerns. Reusable from any RCA/bugfix skill (sherlock, fuzzbug-fix, triage) and standalone.

Analyze and fix a bug found by a fuzzer, fuzzbug, fuzz crash

Push a commit to try on multiple Firefox branches (beta, release, ESR). Use when testing if a patch builds/works on older Firefox versions for uplift.

Update third-party media libraries (libvpx, libdav1d, libaom, libopus, libcubeb, etc.) in the Firefox media/ directory. Use when updating codecs, decoders, or vendored media packages.

Vendor code from a local repository into Firefox's third_party/rust directory.

Create a commit or patch file for Firefox contributions