electron-debug
Skill1 starsChanged 4 months agoMITView on GitHub
Use when an Electron failure or confirmed review finding can be reproduced and needs root-cause analysis, a minimal fix, and regression verification. Do not use for speculative cleanup, broad refactoring, initial review, or masking failures by weakening safeguards.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-releaseSkill
- 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
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 the sidecar handoff when present, review finding, matching track/task, logs, and references/debug-playbook.md.
- Distinctive: line 15
Write a failing regression test/reproducer, observe the intended failure, then apply the smallest fix.
- Distinctive: line 16
Run targeted and broader verification, applicable security checks, and remove temporary instrumentation.
- Distinctive: line 21
Never substitute fixed sleeps, swallowed errors, disabled tests, dependency-wide upgrades, or weakened Electron security for a root-cause …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Electron Debug
Prove the root cause before changing production behavior.
- Read the sidecar handoff when present, review finding, matching track/task,
logs, and
references/debug-playbook.md. - Reproduce the original symptom and capture environment, process, exact input, and raw error without sensitive payloads.
- Classify main, preload, renderer, utility/worker, native module, packaging, update, CI, or platform integration.
- Trace backward across boundaries; form one falsifiable hypothesis at a time and gather discriminating evidence.
- Write a failing regression test/reproducer, observe the intended failure, then apply the smallest fix.
- Run targeted and broader verification, applicable security checks, and remove temporary instrumentation.
- Reopen or advance the affected lane task and record cause, Red/Green evidence, residual risk, and review conclusion in its Evidence, Review, and Result sections.
Never substitute fixed sleeps, swallowed errors, disabled tests, dependency-wide upgrades, or weakened Electron security for a root-cause fix.
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.