deploy-electron

Package and publish Electron applications to GitHub Releases with branch-aware prerelease handling.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/tachiiri-org/agent-ops --skill deploy-electron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-electron
Source: https://github.com/tachiiri-org/agent-ops/tree/main/.codex/skills/deploy-electron
Command: npx skills add https://github.com/tachiiri-org/agent-ops --skill deploy-electron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and profiles (resource) and principles (resource) components.

What problem does it solve?

This Skill automates the process of packaging and publishing Electron applications to GitHub Releases, including handling pre-release versions based on the Git branch.

Core Features & Use Cases

  • Automated Packaging: Builds and packages Electron applications for distribution.
  • GitHub Release Management: Creates and uploads releases to GitHub, including draft pre-releases.
  • Version Management: Reads version from package.json and checks for existing tags.
  • Use Case: After merging changes to the main branch, this Skill can automatically create a stable release on GitHub. For features developed on a separate branch, it can create a draft pre-release.

Quick Start

Use the deploy-electron skill to package and publish the current version of the Electron app to GitHub Releases.

Frequently Asked Questions about deploy-electron

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Electron app deployment to GitHub Releases?

Automating Electron app deployment to GitHub Releases is handled by packaging the application and publishing it directly, using automated version checks from package.json to create either stable releases or draft pre-releases.

How does branch-aware prerelease handling work for Electron publishing?

Branch-aware prerelease handling for Electron publishing creates stable GitHub Releases when pushing to the main branch, while generating draft pre-releases for features developed on separate Git branches.

How do I build and package Electron apps deterministically using electron-builder?

Building and packaging Electron apps deterministically uses `bun run build` and `bun run dist` or `electron-builder` to execute the build process, with specific error handling for build failures and automatic generation of updater metadata.

Can I manage GitHub Release versions automatically from package.json?

Managing GitHub Release versions automatically from package.json reads the version field to check for existing Git tags, ensuring that only new versions are packaged and published to GitHub Releases.

What happens when an Electron build fails during the release process?

When an Electron build fails during the release process, specific error handling is triggered to catch the failure, preventing a broken package from being published to GitHub Releases.

Does the deploy-electron skill generate auto-update metadata for Electron apps?

The deploy-electron skill automatically generates updater metadata during the packaging and publishing process, ensuring Electron applications distributed via GitHub Releases can check for future updates.