electron-release
Skill1 starsChanged 4 months agoMITView on GitHub
Use when an accepted Electron work item needs packaging configuration, versioning, signing/notarization readiness, artifact checks, update metadata, or a Windows/macOS/Linux release matrix. Do not use to publish, upload, or claim unrun platform builds.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- laststance/skillstheir own version, first seen Sep 21, 2026
- FelipeAngeli/skillstheir own version, first seen Apr 10, 2026
- pedronauck/skillstheir own version, first seen Apr 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- pedronauck/skills★ 649same name
- FelipeAngeli/skills★ 2same name
- laststance/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- electron-debugSkill
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-reviewSkill
- electron-test-e2eSkill
- github-deliverySkill
- handoffSkill
- handonSkill
- making-thingsSkill
- mts-moreSkill
- mts-oneSkill
- mts-splitSkill
- product-prdSkill
- solution-architectureSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read sidecar integration task evidence, review findings, references/release-standard.md, and references/release-matrix.md.
- Distinctive: line 21
Do not create a formal Release, upload an installer, publish a package, alter signing credentials, or infer another platform's success.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Electron Release
Prepare and verify packages without turning readiness into publication authority.
- Read sidecar integration task evidence, review findings,
references/release-standard.md, andreferences/release-matrix.md. - Detect the existing builder, scripts, targets, architectures, native rebuild, ASAR/fuses, update provider, and CI. Preserve established choices.
- Record version, changelog, migrations, backup/rollback, channels, and minimum OS/runtime support.
- Require complete declared frontend/backend deliverables and integration verification before release readiness. Run only package/smoke commands that exist in the target repository and are in the authorized scope.
- Record secret variable names as
PRESENT/MISSINGonly; never print values. - Build official artifacts on matching runners when required, then record command/run, signing/notarization, checksum, and smoke evidence per target.
- Attach readiness or blockers to the integration task Result; use
NOT RUNfor missing platform evidence.
Do not create a formal Release, upload an installer, publish a package, alter signing credentials, or infer another platform's success.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.