claudecode-omc 4.8.4 → 4.9.4

package/scripts/build-gemini-server.mjs

@@ -1,74 +0,0 @@
-#!/usr/bin/env node
-/**
- * Build script for standalone Gemini MCP server bundle
- * Bundles the Gemini MCP server into a standalone JS file for plugin distribution
- */
-
-import * as esbuild from 'esbuild';
-import { mkdir, readdir, readFile } from 'fs/promises';
-import { basename, join } from 'path';
-
-// Output to bridge/ directory (not gitignored) for plugin distribution
-const outfile = 'bridge/gemini-server.cjs';
-
-// Scan agents/*.md at build time to embed roles and prompts in the bundle.
-// This eliminates fragile runtime filesystem scanning from CJS bundles.
-const agentFiles = (await readdir('agents')).filter(f => f.endsWith('.md')).sort();
-const agentRoles = agentFiles.map(f => basename(f, '.md'));
-
-// Read and strip frontmatter from each agent prompt
-const agentPrompts = {};
-for (const file of agentFiles) {
-  const content = await readFile(join('agents', file), 'utf-8');
-  const match = content.match(/^---[\s\S]*?---\s*([\s\S]*)$/);
-  agentPrompts[basename(file, '.md')] = match ? match[1].trim() : content.trim();
-}
-console.log(`Embedding ${agentRoles.length} agent roles + prompts into ${outfile}`);
-
-// Ensure output directory exists
-await mkdir('bridge', { recursive: true });
-
-// Preamble: resolve global npm modules so externalized native packages
-// (like @ast-grep/napi) can be found when running from plugin cache
-const banner = `
-// Resolve global npm modules for native package imports
-try {
-  var _cp = require('child_process');
-  var _Module = require('module');
-  var _globalRoot = _cp.execSync('npm root -g', { encoding: 'utf8', timeout: 5000 }).trim();
-  if (_globalRoot) {
-    var _sep = process.platform === 'win32' ? ';' : ':';
-    process.env.NODE_PATH = _globalRoot + (process.env.NODE_PATH ? _sep + process.env.NODE_PATH : '');
-    _Module._initPaths();
-  }
-} catch (_e) { /* npm not available - native modules will gracefully degrade */ }
-`;
-
-await esbuild.build({
-  entryPoints: ['src/mcp/gemini-standalone-server.ts'],
-  bundle: true,
-  platform: 'node',
-  target: 'node18',
-  format: 'cjs',
-  outfile,
-  banner: { js: banner },
-  // Inject build-time constants: agent roles list and prompt contents
-  define: {
-    '__AGENT_ROLES__': JSON.stringify(agentRoles),
-    '__AGENT_PROMPTS__': JSON.stringify(agentPrompts),
-  },
-  // Prefer ESM entry points so UMD packages (e.g. jsonc-parser) get properly bundled
-  mainFields: ['module', 'main'],
-  // Externalize Node.js built-ins and native modules
-  external: [
-    'fs', 'path', 'os', 'util', 'stream', 'events',
-    'buffer', 'crypto', 'http', 'https', 'url',
-    'child_process', 'assert', 'module', 'net', 'tls',
-    'dns', 'readline', 'tty', 'worker_threads',
-    // Native modules that can't be bundled
-    '@ast-grep/napi',
-    'better-sqlite3',
-  ],
-});
-
-console.log(`Built ${outfile}`);

package/scripts/test-codex-gemini-team.mjs

@@ -1,78 +0,0 @@
-#!/usr/bin/env node
-/**
- * Live test: spawn a 2-worker tmux team with Codex + Gemini CLI workers.
- * Must be run inside tmux. Panes will appear in the current window.
- * Usage: node scripts/test-codex-gemini-team.mjs
- */
-import { startTeam, monitorTeam, shutdownTeam } from '../dist/team/runtime.js';
-
-const CWD = process.cwd();
-
-const config = {
-  teamName: 'cgtest',
-  workerCount: 2,
-  agentTypes: ['codex', 'gemini'],
-  tasks: [
-    {
-      subject: 'Write a haiku about tmux split panes',
-      description: [
-        'Write a haiku (3 lines, 5-7-5 syllables) about tmux split panes.',
-        'Save the haiku to the file: ' + CWD + '/done.json',
-        'The file should be valid JSON: {"taskId":"1","status":"completed","summary":"<your haiku here>","completedAt":"' + new Date().toISOString() + '"}',
-        'Write the file and exit.',
-      ].join(' '),
-    },
-    {
-      subject: 'Write a haiku about AI collaboration',
-      description: [
-        'Write a haiku (3 lines, 5-7-5 syllables) about AI models collaborating.',
-        'Save the haiku to the file: ' + CWD + '/farewell.txt',
-        'The file should contain just the haiku text.',
-        'Write the file and exit.',
-      ].join(' '),
-    },
-  ],
-  cwd: CWD,
-};
-
-console.log('\n🚀 Starting tmux team "cgtest" with Codex + Gemini workers...\n');
-
-const runtime = await startTeam(config);
-
-console.log('✅ Team started!');
-console.log(`   tmux target  : ${runtime.sessionName}`);
-console.log(`   workers      : ${runtime.workerNames.join(', ')}`);
-console.log(`   pane IDs     : ${runtime.workerPaneIds.join(', ')}`);
-console.log('\n⏳ Monitoring... (polling every 5s, timeout 120s)\n');
-
-const deadline = Date.now() + 120_000;
-let done = false;
-
-while (Date.now() < deadline && !done) {
-  await new Promise(r => setTimeout(r, 5000));
-  const snap = await monitorTeam(runtime.teamName, runtime.cwd, runtime.workerPaneIds);
-  const { pending, inProgress, completed, failed } = snap.taskCounts;
-  console.log(`   [${new Date().toLocaleTimeString()}] phase=${snap.phase}  pending=${pending} inProgress=${inProgress} completed=${completed} failed=${failed}`);
-  snap.deadWorkers.forEach(w => console.log(`   ⚠️  dead worker: ${w}`));
-  if (snap.phase === 'completed' || snap.phase === 'failed') {
-    done = true;
-  }
-}
-
-if (!done) {
-  console.log('\n⚠️  Timeout — shutting down anyway\n');
-}
-
-console.log('\n🛑 Shutting down team...');
-await shutdownTeam(runtime.teamName, runtime.sessionName, runtime.cwd, 15_000, runtime.workerPaneIds, runtime.leaderPaneId);
-console.log('✅ Team shut down cleanly.\n');
-
-// Show results
-import { readFileSync, existsSync } from 'fs';
-if (existsSync(CWD + '/done.json')) {
-  const d = JSON.parse(readFileSync(CWD + '/done.json', 'utf-8'));
-  console.log('📄 Codex result (done.json):', d.summary || d);
-}
-if (existsSync(CWD + '/farewell.txt')) {
-  console.log('📄 Gemini result (farewell.txt):\n' + readFileSync(CWD + '/farewell.txt', 'utf-8'));
-}

package/skills/skill-development/SKILL.md

@@ -1,218 +0,0 @@
----
-name: skill-development
-description: This skill should be used when the user wants to "create a skill", "write a new skill", "add a skill", or "improve an existing skill". Covers structure, description quality, progressive disclosure, and the quality pipeline.
----
-
-# Writing Skills for Claude Code (OMC)
-
-Guide for creating effective skills in the oh-my-claudecode (OMC) environment. Skills are modular `.claude/skills/<name>/SKILL.md` files that teach Claude specialized workflows, domain knowledge, and tool integrations.
-
-## Agent Workflow
-
-Follow this **Hybrid Workflow** for every skill creation or improvement task:
-
-1. **Requirement Gathering (Soft)**: Before writing anything, ask for **concrete trigger examples**.
-   - *Agent Question*: "Give me 3 exact phrases a user would say to trigger this skill."
-   - These become the quoted trigger phrases in the description.
-2. **Structural Planning (Hard)**: Decide the file structure based on complexity.
-   - Simple knowledge or utility → just `SKILL.md`
-   - Workflow with detailed reference content → `SKILL.md` + `references/`
-   - Script-heavy → add `scripts/`
-3. **Implementation**: Write with correct YAML frontmatter and consistent body format.
-
-## Integration with the OMC Skill Pipeline
-
-This skill is the **entry point**. After creating or editing a skill, run:
-
-1. `skill-development` — create/author the skill (this skill)
-2. `skill-quality-analyzer` — score it across 6 dimensions (target ≥80)
-3. `skill-debugger` — check if description triggers correctly
-4. `skill-tester` — verify behavioral correctness
-
-## Anatomy of an OMC Skill
-
-```
-skill-name/               ← folder name = YAML name (kebab-case)
-├── SKILL.md              ← required; ≤200 lines ideally
-└── references/           ← optional; detailed content loaded on demand
-    ├── patterns.md
-    └── examples.md
-```
-
-### SKILL.md (required)
-
-**Frontmatter**: The `description` field is what Claude sees in the system-reminder when deciding whether to invoke the skill. Make it specific.
-
-Two formats for the description:
-
-```yaml
-# For skills intended for auto-discovery (user/project skills):
-description: "This skill should be used when the user asks to 'trigger phrase 1', 'trigger phrase 2', 'trigger phrase 3'."
-
-# For OMC core workflow skills (already triggered by CLAUDE.md keywords):
-description: "Concise capability summary. Triggered by: 'keyword1', 'keyword2'."
-```
-
-**Body formats** — choose one and be consistent:
-
-- **XML tags** (for workflow/process skills): `<Purpose>`, `<Use_When>`, `<Do_Not_Use_When>`, `<Steps>`, `<Examples>`, `<Final_Checklist>`, `<Advanced>`
-- **Markdown headers** (for utility/reference skills): `## When to Use`, `## Workflow`, `## Examples`
-
-See `references/format-guide.md` for complete tag-by-tag reference.
-
-### references/ (optional)
-
-Load only when Claude determines it's needed during execution.
-
-- **When to use**: SKILL.md body would exceed ~200 lines without it
-- **Move here**: detailed patterns, API references, advanced techniques, long examples
-- **Keep in SKILL.md**: core workflow, quick reference tables, pointers to references/
-
-### Progressive Disclosure
-
-Skills use a three-level loading system:
-
-| Level | What loads | When |
-|-------|-----------|------|
-| Metadata | `name` + `description` | Always |
-| Body | SKILL.md content | When skill triggers |
-| References | `references/*.md` | When Claude reads them |
-
-## Skill Creation Process
-
-### Step 1: Understand the Use Case
-
-Skip only when usage patterns are completely clear.
-
-Ask for concrete examples:
-- "What would a user say to trigger this skill?"
-- "What's the main output or artifact it produces?"
-- "What should it NOT do?" (defines `<Do_Not_Use_When>`)
-
-Aim for 3 trigger phrases before writing any content.
-
-### Step 2: Plan the Structure
-
-Analyze each concrete example:
-1. What would Claude need to execute this from scratch?
-2. What reference material would help if repeated?
-3. Any scripts or assets needed?
-
-### Step 3: Write the Description
-
-**Hard rule**: The description must contain quoted trigger phrases.
-
-```yaml
-# ✅ Good — specific trigger phrases, third person, summary at end
-description: "This skill should be used when the user asks to 'create a validation rule', 'define trigger conditions', or 'validate tool instructions'. Provides comprehensive guidance with clear trigger phases and quality gates."
-
-# ❌ Bad — vague, no trigger phrases, wrong person
-description: Use this skill when working with hooks.
-description: Provides hook guidance.
-```
-
-### Step 4: Write the Body
-
-**Style**: Imperative/infinitive form, not second person.
-
-```
-✅ "Start by reading the configuration file."
-✅ "Validate the input before processing."
-❌ "You should start by reading the configuration file."
-❌ "You need to validate the input."
-```
-
-**Size target**: ≤200 lines for SKILL.md body. Move detail to `references/` if exceeded.
-
-### Step 5: Validate
-
-Run `skill-quality-analyzer` on the new skill. Target score ≥80.
-
-Check the description manually:
-```bash
-grep "^description:" skills/<name>/SKILL.md
-# Verify it contains quoted trigger phrases
-```
-
-Check line count:
-```bash
-wc -l skills/<name>/SKILL.md
-# Target: ≤200
-```
-
-### Step 6: Iterate
-
-After using the skill on real tasks:
-- Notice struggles or missed triggers
-- Strengthen description with additional trigger phrases
-- Move long sections to `references/` if context bloat is observed
-- Add missing edge cases to `<Do_Not_Use_When>`
-
-## Validation Checklist
-
-**Frontmatter:**
-- [ ] `name` matches folder name exactly (kebab-case)
-- [ ] `description` contains at least 2 quoted trigger phrases
-- [ ] Description is ≤200 characters
-
-**Content:**
-- [ ] Body uses imperative form (not "you should")
-- [ ] SKILL.md ≤200 lines (move detail to references/ if not)
-- [ ] Referenced files in `references/` actually exist
-- [ ] No platform-specific branding (e.g., "Codex CLI")
-
-**Quality:**
-- [ ] `skill-quality-analyzer` score ≥80
-- [ ] `<Do_Not_Use_When>` or equivalent section present (prevents misuse)
-- [ ] At least 3 usage examples (Good + Bad preferred)
-
-## Common Mistakes
-
-### Mistake 1: Weak trigger description
-
-```yaml
-# ❌ Bad
-description: Provides guidance for working with hooks.
-
-# ✅ Good
-description: "This skill should be used when the user asks to 'create a hook', 'add a pre-tool hook', or 'set up hook validation'. Full hook development guide with examples and scripts."
-```
-
-### Mistake 2: Everything in SKILL.md
-
-```
-# ❌ Bad
-skill-name/
-└── SKILL.md  (900 lines — everything in one file)
-
-# ✅ Good
-skill-name/
-├── SKILL.md         (180 lines — core workflow)
-└── references/
-    ├── patterns.md  (250 lines)
-    └── advanced.md  (300 lines)
-```
-
-### Mistake 3: Second-person writing
-
-```
-# ❌ Bad
-You should start by reading the config file.
-You need to validate the input.
-
-# ✅ Good
-Start by reading the config file.
-Validate the input before processing.
-```
-
-## Additional Resources
-
-- `references/format-guide.md` — complete XML tag reference, style rules, size targets
-- `references/description-patterns.md` — Good/Bad description catalog for all OMC skill categories
-
-## Related Skills
-
-- `skill-quality-analyzer` — score a skill across 6 quality dimensions
-- `skill-debugger` — debug why a skill isn't triggering
-- `skill-tester` — verify a skill triggers and behaves correctly
-- `skill` — manage installed skills (list, add, remove, sync)

package/skills/skill-development/references/description-patterns.md

@@ -1,160 +0,0 @@
-# Description Patterns — Good/Bad Catalog
-
-Reference for writing the `description` field in SKILL.md frontmatter.
-
-Claude sees this description in the system-reminder when deciding whether to invoke a skill.
-Format: `"This skill should be used when the user asks to '[trigger]', '[trigger]'. [Summary]."`
-
----
-
-## The Format Standard
-
-```yaml
-# Auto-discovery skills (user/project skills):
-description: "This skill should be used when the user asks to '[trigger 1]', '[trigger 2]', or '[trigger 3]'. [One-sentence summary]."
-
-# OMC core workflow skills (also triggered by CLAUDE.md keywords):
-description: "[Capability summary]. Triggered by: '[kw1]', '[kw2]'."
-```
-
-**Required**: At least 2 quoted trigger phrases using `'single quotes'`.
-
----
-
-## Anti-Pattern Catalog
-
-### Anti-pattern 1: Tagline instead of trigger
-
-```yaml
-# ❌ Tagline — describes what it IS, not WHEN to use it
-description: Full autonomous execution from idea to working code
-description: Parallel execution engine for high-throughput task completion
-description: Self-referential loop until task completion with architect verification
-
-# ✅ Trigger-forward
-description: "Use when user wants full-auto development ('build me', 'autopilot', 'I want a'). End-to-end pipeline from idea to verified code."
-description: "Use when running multiple independent tasks in parallel ('ulw', 'ultrawork', 'run in parallel'). Tiered agent routing with haiku/sonnet/opus."
-description: "Use when task must complete guaranteed ('ralph', 'don't stop', 'must complete'). Persistence loop with architect sign-off."
-```
-
-### Anti-pattern 2: Wrong platform branding
-
-```yaml
-# ❌ Platform-specific (Codex, not Claude Code)
-description: Analyzes Codex skill quality with 6-dimension scoring system
-description: Tests Codex skill functionality with TDD approach
-
-# ✅ Platform-neutral
-description: "This skill should be used when the user asks to 'analyze skill quality', 'score skill', or 'skill quality report'. 6-dimension scoring for Claude Code skills."
-description: "This skill should be used when the user asks to 'test skill', 'verify skill', or 'skill test'. Trigger tests and behavioral validation for Claude Code skills."
-```
-
-### Anti-pattern 3: Second person in description
-
-```yaml
-# ❌ Second person
-description: Use this skill when you want to plan before coding
-description: Load this skill when user asks for parallel execution
-
-# ✅ Third person or neutral
-description: "This skill should be used when the user asks to 'plan this', 'plan the', or 'let's plan'. Interview, direct, consensus, and review modes."
-```
-
-### Anti-pattern 4: No trigger phrases (vague)
-
-```yaml
-# ❌ Vague — no specific triggers
-description: Helps with various tasks
-description: Provides guidance for working with hooks
-description: Deep analysis and investigation
-
-# ✅ Specific
-description: "This skill should be used when the user asks to 'create a hook', 'add validation hook', or 'configure hook behavior'. Full hook development with examples."
-description: "Use when debugging or investigating failures ('analyze', 'debug', 'investigate', 'why is this failing'). Delegates to debugger agent for root-cause analysis."
-```
-
----
-
-## Pattern Catalog by Category
-
-### Workflow / Orchestration Skills
-
-These are invoked by keyword — triggers must match CLAUDE.md `<skills>` section keywords.
-
-```yaml
-# autopilot
-description: "Use when user wants full-auto development ('build me', 'autopilot', 'I want a', 'create me'). End-to-end: spec→plan→code→QA→validation with no manual intervention."
-
-# ralph
-description: "Use when task must complete guaranteed ('ralph', 'don't stop', 'must complete', 'finish this'). Persistence loop with ultrawork parallelism and architect sign-off."
-
-# ultrawork
-description: "Use when running multiple independent tasks in parallel ('ulw', 'ultrawork', 'run in parallel'). Tiered agent routing: haiku/sonnet/opus fired simultaneously."
-
-# plan
-description: "Use when planning before coding ('plan this', 'plan the', 'let's plan', 'make a plan'). Interview, direct, consensus (--consensus), and review (--review) modes."
-
-# team
-description: "Use when coordinating multiple agents on a project ('team', 'coordinated team', 'multi-agent', 'swarm'). TeamCreate→tasks→parallel agents→verify→TeamDelete pipeline."
-```
-
-### Quality / Skill Tooling
-
-```yaml
-# writing-skills
-description: "This skill should be used when the user asks to 'create a skill', 'write a new skill', 'add a skill', or 'improve an existing skill'. Covers structure, description quality, progressive disclosure, and the quality pipeline."
-
-# skill-quality-analyzer
-description: "This skill should be used when the user asks to 'analyze skill quality', 'score skill', 'skill quality report', or 'audit skill'. 6-dimension scoring: clarity, structure, examples, triggers, practices, maintainability."
-
-# skill-debugger
-description: "This skill should be used when the user asks to 'debug skill', 'skill not triggering', 'why isn't skill working', or 'skill discovery issue'. Diagnoses description quality, naming, conflicts, and file structure."
-
-# skill-tester
-description: "This skill should be used when the user asks to 'test skill', 'verify skill', 'does this skill trigger', or 'skill test'. Trigger tests, functional tests, and edge case validation."
-```
-
-### Domain / Code Skills
-
-```yaml
-# tdd
-description: "This skill should be used when the user asks to 'tdd', 'test first', 'red green refactor', or 'write tests first'. Enforces Red→Green→Refactor cycle — no implementation before failing test."
-
-# security-review
-description: "This skill should be used when the user asks to 'security review', 'check for vulnerabilities', 'OWASP audit', or 'security scan'. Comprehensive review across OWASP Top 10, authn/authz, and trust boundaries."
-
-# code-review
-description: "This skill should be used when the user asks to 'code review', 'review this PR', 'review code', or 'check my code'. Multi-layer review: style, quality, security, API compatibility, performance."
-
-# ai-commenting
-description: "This skill should be used when the user asks to 'ai comment', 'annotate code', 'add ai tags', or 'mark high-risk code'. Machine-parseable @ai: protocol for risk, intent, deps, auth, invariants."
-```
-
-### Utility / Management Skills
-
-```yaml
-# note
-description: "This skill should be used when the user asks to 'note', 'remember this', 'save note', or 'notepad'. Persists to .omc/notepad.md — survives context compaction."
-
-# cancel
-description: "This skill should be used when the user wants to 'cancel', 'stop', or 'abort' an active OMC mode. Cleanly exits autopilot, ralph, ultrawork, ultraqa, team, pipeline state."
-
-# trace
-description: "This skill should be used when the user asks to 'trace', 'show agent trace', 'what agents ran', or 'session timeline'. Renders timeline of agent calls and results."
-
-# hud
-description: "This skill should be used when the user asks to 'hud', 'configure display', 'hud layout', or 'status bar'. Sets layout, visible elements, and display presets."
-```
-
----
-
-## Quick Self-Check
-
-Before finalizing a description, ask:
-
-1. **Natural?** Would a user actually say these trigger phrases?
-2. **Specific?** Would it distinguish this skill from similar ones?
-3. **Quoted?** Does it contain at least 2 phrases in `'single quotes'`?
-4. **Summarized?** Does the last sentence say what it produces?
-
-If all 4 are yes → the description is ready.