firefox-wiki

firefox-wiki-plugin

A Claude Code plugin that gives Claude a persistent memory of Firefox media subsystem knowledge — so it stops redoing the same code archaeology every investigation and builds on what it already knows.

Without this plugin, Claude re-searches the same components, re-reads the same files, and re-derives the same facts every session. With it, knowledge accumulates: every investigation adds to the wiki, and every future investigation starts from what was already learned.

The wiki content is maintained in a shared private repo. You need access to get the accumulated knowledge — without it you start from an empty wiki and lose the team's prior learnings. Request access from :alwu ([email protected]) before installing.

How it works

The whole plugin is one idea: read the wiki before doing code archaeology, write back what you learn after. You never run anything — hooks do both halves automatically, so each bug starts from everything earlier bugs taught Claude instead of re-deriving it.

flowchart LR
    Bug["You work a bug<br/>(investigate · triage · review)"]
    W[("Firefox Wiki")]
    Bug -->|"① before searching code,<br/>a hook checks the wiki"| W
    W -->|"if known: read cited facts,<br/>often skip the search"| Bug
    Bug -->|"② on commit, a hook writes<br/>back what was learned"| W
    W -->|"next bug starts<br/>from prior knowledge"| Bug

The four hooks, in plain terms

When it fires	What it does for you
Before a code search (searchfox-cli, or grep under a watched path)	Checks the wiki first. If it has the answer, Claude reads the cited facts and may skip the search. Query terms are alias- and Class::Method-expanded, so jargon like MDSM still finds MediaDecoderStateMachine.
After a commit in a source repo	Reads the diff/investigation, extracts the durable facts, and saves them for next time.
After any write to the wiki	A quick lint pass flags broken links and stale references.
During a tracked skill (bug-start, triage, review-patch, analyze-profile, …)	Tags any wiki use with that skill, so /firefox-wiki:stats can tell you which kinds of work actually consult the wiki.

That's it — install it and work normally; the loop runs in the background.

Two manual levers when you want them:

• Add knowledge yourself — a spec URL, a bug, or a plain fact — with /firefox-wiki:add.
• Tune what triggers the hooks (search tool, watched paths) and where the wiki lives — see Configuration. The tracked-skill list is scripts/wiki-relevant-skills.txt (one name per line).

Install

Run these commands in your terminal (not in the Claude Code prompt).

1. Install the plugin — directly from GitHub, no clone needed:

claude plugin marketplace add alastor0325/firefox-wiki-plugin
claude plugin install firefox-wiki@firefox-wiki-plugin

Prefer a local copy to read or hack on? Clone it first and point the marketplace at the clone instead: git clone https://github.com/alastor0325/firefox-wiki-plugin ~/firefox-wiki-plugin && claude plugin marketplace add ~/firefox-wiki-plugin

2. Point it at a wiki — the plugin is the tooling; the content is a separate git repo. Shared vs. personal is only which repo WIKI_PATH names (default ~/firefox-wiki):

# A shared team wiki — clone its content repo (request access; it's private):
git clone https://github.com/alastor0325/firefox-wiki ~/firefox-wiki
# …or your OWN wiki — set WIKI_PATH to your repo (or a fresh dir); init scaffolds it.

3. Initialize (in Claude Code):

/firefox-wiki:init

This verifies dependencies and creates the wiki directory structure. Follow any prompts it shows.

Requirements: jq · pandoc · bmo-to-md

macOS:

brew install jq pandoc && cargo install bmo-to-md

Linux:

sudo apt install jq pandoc && cargo install bmo-to-md   # Debian/Ubuntu
sudo dnf install jq pandoc && cargo install bmo-to-md   # Fedora

Windows:

winget install jqlang.jq JohnMacFarlane.Pandoc && cargo install bmo-to-md

---

Commands

Command	Purpose
/firefox-wiki:init	One-time setup
/firefox-wiki:add <input>	Add a spec, bug, or fact to the wiki
/firefox-wiki:stats	View usage metrics and lookup hit rate

Adding knowledge

/firefox-wiki:add accepts several input types:

Input	What happens
https://...	Fetches and distills into specs/
/path/to/file.pdf	Reads PDF and distills into specs/
bug 2026875	Extracts knowledge from the bug
Natural language	Writes to components/, relations/, or patterns/

/firefox-wiki:add https://www.w3.org/TR/media-source/
/firefox-wiki:add bug 2026875
/firefox-wiki:add AudioSink runs on the MDSM task queue, not its own thread

Skills that run automatically