skills.rest
rubrical-works
rubrical-worksOFFICIAL
Explore all skills by this author →
GitHub

electron-error-capture

Captures Electron app errors via Playwright during manual sessions and generates timestamped reports.

Updated Mar 30, 2026
Search Tags:#debugging#playwright#electron#e2e testing#bug reproduction#error capture#crash reporting
One-click install
npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill electron-error-capture-rubrical-works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: electron-error-capture
Source: https://github.com/rubrical-works/idpf-praxis-skills/tree/main/Skills/electron-error-capture
Command: npx skills add https://github.com/rubrical-works/idpf-praxis-skills --skill electron-error-capture-rubrical-works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, electron, and includes scripts (resource) components.

What problem does it solve? Errors in Electron apps are often transient — visible in DevTools for a moment, then gone before you can act. This Skill fills the gap between ephemeral DevTools watching and scripted E2E tests by recording every page error, console error, renderer crash, and main-process stderr line while you drive the app by hand, then producing a report you can paste into a bug. ## Core Features & Use Cases - Five observed capture channels: page errors, console errors, console warnings (opt-in), renderer crashes, and main-process stderr, each wired to a real Playwright or process hook. - Derived classifications: unhandled promise rejections, IPC failures, and CSP violations are pattern-matched over captured lines and clearly labeled as inferred rather than observed. - Timestamped report output: each session writes report.md, report.json, a session log, and per-error screenshots into a timestamped directory so previous sessions are preserved. - Use Case: While reproducing an intermittent bug before a release, launch the harness, click through the app normally, press Ctrl+C, and hand the generated markdown report with screenshots to the team. ## Quick Start Ask Claude to run the electron-error-capture skill from your Electron project root, then interact with the launched app and press Ctrl+C to generate the error report.

Frequently Asked Questions about electron-error-capture

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

FAQPage Schema
How do I capture errors in an Electron app with Playwright?▼

Run the capture-session script from your project root; it launches the app headed via Playwright's _electron API and records page errors, console errors, crashes, and stderr while you interact. Press Ctrl+C or close the window to generate the report.

How to reproduce transient Electron bugs that disappear from DevTools?▼

Use a capture harness that logs every error to disk as it happens instead of watching DevTools. This skill writes each event to a session log in real time and compiles a timestamped markdown and JSON report with screenshots on exit.

Does this tool install Playwright automatically?▼

No, it installs nothing. If @playwright/test does not resolve from the target project, the script stops and directs you to the playwright-setup skill, which owns browser runtime installation.

Can it detect unhandled promise rejections and IPC failures in Electron?▼

Yes, but as inferred classifications, not hooks. It pattern-matches captured console and stderr lines against configurable regex patterns, and the report explicitly labels these as derived rather than directly observed.

Why does electron.launch() hang or time out during capture?▼

A launch hang usually means the EnableNodeCliInspectArguments fuse is off in the Electron binary. Raise the launch timeout with the --timeout flag, or check the app's build configuration.

When should I use E2E tests instead of manual error capture?▼

Use scripted E2E tests for repeatable, deterministic scenarios and CI regression checks. Use manual capture when exploring intermittent behavior or reproducing bugs whose trigger steps are not yet known.

Related Skills

Explore More Software Engineering Skills→
mdmagnuson-creatormdmagnuson-creator

ui-test-electron

Create and run Playwright End-to-End tests for Electron desktop applications.

Community
Advanced
marcusgollmarcusgoll
91

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright projects.

Community
Advanced
coopeverythingcoopeverything

error-learner

Identify error patterns from session transcripts and update knowledge bases.

Community
Advanced
csim-sgcsim-sg

write-e2e-tests

Generate and run Playwright end-to-end tests for the tldraw UI.

Community
Intermediate