What is the primary goal of Phase One in this skill?

Phase One focuses on ensuring all Chromium patches apply correctly using 'e sync --3', resolving any git conflicts, and exporting the results into the Electron repository's patch directory.

Does this skill work for general Electron app development?

No, this skill is specifically designed for maintainers working on the Electron framework itself, specifically for managing the underlying Chromium engine dependency.

Why does the skill emphasize patch hunk header updates?

Modifying one patch often shifts line numbers for others; the skill tracks these secondary changes to prevent 'dirty' repositories and ensure clean future syncs.

How does it handle build failures during an upgrade?

It utilizes 'e build -k 999' to gather maximum error context, identifies whether the fix belongs in Electron's core or a Chromium patch, and guides the user through targeted rebuilds.

Electron Chromium Upgrader

Name: Electron Chromium Upgrader
Author: manageryzy

bymanageryzy

Deployment & DevOps

Guides the process of upgrading the Chromium version within the Electron project by managing patch conflicts and build errors.

About

This skill provides a structured framework for Claude to navigate the multi-phase process of upgrading Electron's Chromium dependency. It orchestrates the complex workflow of Phase One (patch synchronization and 3-way merge conflict resolution) and Phase Two (iterative build error fixing and API adaptation). By enforcing strict patch management rules, standardized commit guidelines, and precise use of the Electron 'e' build tool, it ensures that downstream patches remain stable and compatible with upstream Chromium changes.

Key Features

Iterative build error detection and resolution workflow for Phase Two
Integration with Electron-specific tools like 'e sync' and 'e build'
Step-by-step guidance for Phase One patch synchronization and conflict resolution
Automated patch export and hunk header update management
0 GitHub stars
Standardized commit formatting and patch authorship preservation

Use Cases

Adapting Electron source code to breaking changes in upstream Chromium APIs
Upgrading the Chromium SHA in the roller/chromium/main branch
Resolving complex patch conflicts during the Electron sync process

About

Key Features

Iterative build error detection and resolution workflow for Phase Two
Integration with Electron-specific tools like 'e sync' and 'e build'
Step-by-step guidance for Phase One patch synchronization and conflict resolution
Automated patch export and hunk header update management
0 GitHub stars
Standardized commit formatting and patch authorship preservation

Use Cases

Adapting Electron source code to breaking changes in upstream Chromium APIs
Upgrading the Chromium SHA in the roller/chromium/main branch
Resolving complex patch conflicts during the Electron sync process