End-to-end Chrome security backport for an Electron release branch. Given a Chrome Releases blog URL and a branch (e.g. 41-x-y), determines which CVE fixes are missing from the actual synced source, writes the cherry-pick patches locally, validates them with e sync --3 + lint --patches, then pushes a single PR. Use…
Guide for performing Chromium version upgrades in the Electron project. Use when working on the roller/chromium/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Chromium changes, and proper commit formatting for patch fixes.
Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit…
Use this skill to explain, in plain language, what is wrong with the mx::api round-trip and what it needs next. It drives the failure classifier (dump -> classify) over the corpus, then reads build/api/classified.json and turns it into a prioritized, human-readable worklist grouped by failure shape (crashes, instant…
The mx::api design doctrine. You MUST read this before designing or changing anything in the mx::api layer: adding or reshaping public types in src/include/mx/api/, wiring them through mx::impl, writing comments in api headers, or reviewing any of the above.
Scaffold a new strategy (and optionally environment) model in the plant C++/R package, then wire it through the build. Use when asked to add a new model/strategy, create a strategy from an existing one (e.g. clone FF16), add a variant strategy that reuses an existing environment, or "use the scaffolder". Covers…
Migrate code that uses the plant R package up to plant's latest interface. Use when a downstream product (analysis scripts, a dependent package, a notebook) breaks or needs updating after plant changed — e.g. "update X to the latest plant", "plant's interface changed, fix my code", "migrate to the new runscm/Control…
Profile and benchmark the plant C++/R package — find hotspots, measure whether a change or branch helped or regressed, and compare performance across builds. Use when asked to profile, benchmark, time, or optimize plant; to find what is slow; to compare speed between two branches/commits; or to verify a change did not…
Develop or debug the qb-linq header-only C++17 LINQ library (qb::linq): locate declarations and definitions, extend iterators and views, run qblinqtests and optional benchmarks. Use when editing include/qb/linq, adding terminals or lazy views, or writing tests for this repo.