claudecode-omc 4.8.2 → 4.8.4

package/skills/e2e/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: e2e
+description: Playwright end-to-end orchestration for critical user journeys, artifact capture, flaky-test isolation, and CI-ready reporting.
+---
+
+# E2E
+
+Use this as the top-level end-to-end testing orchestrator.
+
+## Use When
+
+- Validating cross-layer user journeys
+- Preparing release confidence checks
+- Reproducing user-facing regressions
+
+## Workflow
+
+1. Define critical journeys and acceptance assertions.
+2. Generate or update Playwright tests.
+3. Run targeted tests first, then broader suites.
+4. Capture artifacts (trace/screenshot/video/report).
+5. Identify flakes and quarantine when needed.
+
+## Playwright Best Practices
+
+- Test user-visible behavior and assertions.
+- Keep tests isolated and deterministic.
+- Prefer resilient locators (`getByRole`, `getByLabelText`, `getByText`).
+- Use web-first assertions and auto-waiting.
+- Mock or isolate third-party dependencies when they are not under test.
+
+## Suggested Config
+
+```ts
+// playwright.config.ts
+use: {
+  trace: 'retain-on-failure',
+  video: 'retain-on-failure',
+  screenshot: 'only-on-failure',
+},
+retries: process.env.CI ? 2 : 0
+```
+
+## Electron Routing
+
+If the target is an Electron app, use `/oh-my-claudecode:electron-driver` as the runtime backend while keeping Playwright assertions and artifacts.
+
+## References
+
+- Best practices: https://playwright.dev/docs/best-practices
+- Actionability / auto-waiting: https://playwright.dev/docs/actionability
+- Trace viewer: https://playwright.dev/docs/trace-viewer
+- Retries and flaky handling: https://playwright.dev/docs/test-retries
+- Codegen: https://playwright.dev/docs/codegen-intro
+

package/skills/electron-driver/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: electron-driver
+description: Playwright-based E2E driving for Electron applications using launch mode or attach mode with robust window selection and runtime inspection.
+---
+
+# Electron Driver
+
+Use this skill for Electron runtime automation and debugging.
+
+## Modes
+
+- Launch mode (preferred for clean CI runs)
+- Attach mode (preferred for debugging existing sessions)
+
+## Prerequisites
+
+```bash
+pnpm add -D playwright-core @playwright/test
+```
+
+## Launch Mode (recommended)
+
+```ts
+import { _electron as electron } from 'playwright';
+
+const electronApp = await electron.launch({ args: ['.'] });
+const page = await electronApp.firstWindow();
+```
+
+Use locators on `page` for UI actions and assertions.
+
+## Attach Mode
+
+- Start Electron with `--remote-debugging-port=<port>`
+- Connect via CDP and pick the non-`devtools://` page
+
+Template: `skills/electron-driver/scripts/driver-template.js`
+
+## Best Practices
+
+- Filter out DevTools pages before interaction.
+- Use role/text-based locators for resilience.
+- Keep launch mode for stable regression suites.
+- Use attach mode for live bug reproduction.
+- Capture trace/screenshot artifacts for failures.
+
+## References
+
+- Playwright Electron API: https://playwright.dev/docs/api/class-electron
+- Electron automated testing: https://www.electronjs.org/docs/latest/tutorial/automated-testing
+

package/skills/electron-driver/scripts/driver-template.js

@@ -0,0 +1,46 @@
+const { chromium } = require('playwright-core');
+
+/**
+ * Electron attach-mode template.
+ *
+ * Usage:
+ * 1) Start Electron with --remote-debugging-port=<PORT>
+ * 2) Optionally set CDP_PORT env var
+ * 3) Run: node skills/electron-driver/scripts/driver-template.js
+ */
+
+const CDP_PORT = process.env.CDP_PORT || 9222;
+const CDP_URL = `http://localhost:${CDP_PORT}`;
+
+async function run() {
+  let browser;
+  try {
+    browser = await chromium.connectOverCDP(CDP_URL);
+    const context = browser.contexts()[0];
+    if (!context) throw new Error('No browser context found');
+
+    const page = context.pages().find((p) => !p.url().startsWith('devtools://'));
+    if (!page) throw new Error('No Electron app page found');
+
+    console.log(
+      JSON.stringify({
+        status: 'success',
+        title: await page.title(),
+        url: page.url(),
+      })
+    );
+  } catch (error) {
+    console.error(
+      JSON.stringify({
+        status: 'error',
+        message: error.message,
+      })
+    );
+    process.exitCode = 1;
+  } finally {
+    if (browser) await browser.close();
+  }
+}
+
+run();
+

package/skills/multi-model-research/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: multi-model-research
+description: Run structured multi-model research (Claude, Gemini, Codex) and synthesize consensus, disagreements, and final recommendations.
+---
+
+# Multi-Model Research
+
+Use this skill for architecture choices, tradeoff analysis, or high-stakes technical decisions.
+
+## Use When
+
+- The user asks for multi-model research, technology selection, or architecture comparison
+- A decision has competing options and needs cross-model critique
+- You need confidence checks before implementation
+
+## Workflow
+
+1. Define the research question:
+   - Decision to make
+   - Constraints
+   - Evaluation criteria (performance, maintainability, cost, risk)
+2. Query providers with the same prompt template:
+   - `omc ask claude "<question>"`
+   - `omc ask gemini "<question>"`
+   - `omc ask codex "<question>"`
+3. Normalize each answer into:
+   - Proposed approach
+   - Key arguments
+   - Risks and unknowns
+4. Synthesize:
+   - Consensus points
+   - Contradictions
+   - Missing evidence
+   - Final recommendation with rationale
+5. Record artifacts and next validation steps.
+
+## Quality Rules
+
+- Keep prompts equivalent across models to reduce bias.
+- Cite concrete evidence, not authority.
+- Separate facts from inference.
+- If a provider is unavailable, continue and clearly state the reduced confidence.
+
+## Output Format
+
+- Research question and criteria
+- Per-model findings
+- Consensus and disagreements
+- Recommended decision
+- Validation checklist and follow-up experiments
+

package/skills/omc-doctor/SKILL.md

@@ -101,10 +101,10 @@ ls -la ~/.claude/skills/ 2>/dev/null
 - If custom files exist that do NOT match plugin names: OK - these are user custom content, do not flag them
 
 **Known plugin agent names** (check agents/ for these):
-`architect.md`, `document-specialist.md`, `explore.md`, `executor.md`, `debugger.md`, `planner.md`, `analyst.md`, `critic.md`, `verifier.md`, `test-engineer.md`, `build-fixer.md`, `designer.md`, `writer.md`, `qa-tester.md`, `scientist.md`, `security-reviewer.md`, `code-reviewer.md`, `quality-reviewer.md`, `deep-executor.md`
+`architect.md`, `document-specialist.md`, `explore.md`, `executor.md`, `debugger.md`, `planner.md`, `analyst.md`, `critic.md`, `verifier.md`, `test-engineer.md`, `designer.md`, `writer.md`, `qa-tester.md`, `scientist.md`, `security-reviewer.md`, `code-reviewer.md`, `git-master.md`, `code-simplifier.md`
 
 **Known plugin skill names** (check skills/ for these):
-`autopilot`, `ralph`, `ultrawork`, `team`, `ultrapilot`, `pipeline`, `ultraqa`, `plan`, `ralplan`, `analyze`, `build-fix`, `cancel`, `ccg`, `code-review`, `configure-notifications`, `configure-openclaw`, `deepinit`, `external-context`, `hud`, `learn-about-omc`, `learner`, `mcp-setup`, `note`, `omc-doctor`, `omc-help`, `omc-setup`, `omc-teams`, `project-session-manager`, `ralph-init`, `release`, `review`, `sciomc`, `security-review`, `skill`, `tdd`, `trace`, `writer-memory`
+`ai-slop-cleaner`, `ask`, `autopilot`, `cancel`, `ccg`, `configure-notifications`, `deep-interview`, `deepinit`, `external-context`, `hud`, `learner`, `mcp-setup`, `omc-doctor`, `omc-setup`, `omc-teams`, `plan`, `project-session-manager`, `ralph`, `ralplan`, `release`, `sciomc`, `setup`, `skill`, `team`, `ultraqa`, `ultrawork`, `writer-memory`
 
 **Known plugin command names** (check commands/ for these):
 `ultrawork.md`, `deepsearch.md`