What problem does it solve?
Manually mapping Chrome security release blog posts to Electron release branches, identifying which CVE fixes are already present, and producing conflict-free cherry-pick patches is error-prone and time-consuming. This Skill automates the entire backport workflow from CVE-to-CL mapping through validated PR creation.
Core Features & Use Cases
- CVE-to-CL Mapping: Parses Chrome Releases blog posts to extract CVE identifiers, associated bugs, severity, and canonical fix CLs from Gerrit.
- In-Tree Verification: Checks the synced Electron source via git log and patch directory greps to determine whether each CVE fix is already present.
- Patch Generation & Validation: Writes cherry-pick patches locally, validates them with
e sync --3 and node script/lint.js --patches, and resolves conflicts (test-only drift, target-milestone merge CLs, or drop-and-flag for manual port).
- PR Creation: Pushes a single backport PR following the Electron PR template with appropriate labels, keeping CVE details out of the public PR body.
Quick Start
Backport the Chrome security release at the provided blog URL to the specified Electron release branch and open a validated PR.