npm - @trac3er/oh-my-god - Versions diffs - 2.2.2 → 2.2.4 - Mend

@trac3er/oh-my-god 2.2.2 → 2.2.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1525) hide show

package/build/lib/commands/OMG:security-check.md DELETED Viewed

@@ -1,28 +0,0 @@
----
-description: "Canonical OMG security pipeline with normalized findings, dependency enrichment, and untrusted-content evidence."
-allowed-tools: Read, Grep, Glob, Bash(python3:*), Bash(pytest:*), Bash(rg:*)
-argument-hint: "[path or '.' for the current project]"
----
-# /OMG:security-check — Canonical Security Pipeline
-Run OMG's canonical security pipeline against the current project or a scoped path.
-## Usage
-```text
-/OMG:security-check
-/OMG:security-check .
-/OMG:security-check app/
-```
-## What It Produces
-- normalized findings across policy, Python AST checks, and dependency health
-- evidence-ready provenance and trust scores
-- a structured result that can be reused by `ship`, the control plane, and the OMG MCP
-## Notes
-- Use this for auth, secrets, untrusted-content, or dependency-risk work.
-- `omg secure --command ...` remains the low-level command-risk primitive, not the full audit surface.

package/build/lib/commands/OMG:session-branch.md DELETED Viewed

@@ -1,101 +0,0 @@
----
-description: "Create or manage OMG state branches for experimental workflows."
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: "--name <branch-name> [--from <snapshot_id>]"
----
-# /OMG:session-branch — Branch OMG State
-Create a named branch of the current OMG state for experimentation or parallel exploration.
-## Scope Statement
-**This command operates on `.omg/state/` only. It does NOT modify git history, workspace files, or conversation history.**
-## Important
-Branching is **OMG state only** — it captures and restores `.omg/state/` directory contents. It does **not** fork the conversation, context window, or Claude session. Think of it as a checkpoint you can name and switch between. Rollback restores OMG session state only, NOT git history or repo files.
-## Usage
-```
-/OMG:session-branch --name "experiment"
-/OMG:session-branch --name "refactor-v2" --from 20260302_143000_baseline
-```
-## What It Does
-1. Creates a snapshot of the current `.omg/state/` directory (or restores a specified snapshot)
-2. Writes branch metadata to `.omg/state/branches/<name>.json`
-3. Updates `.omg/state/current_branch.json` to track the active branch
-## Branch Metadata
-Each branch stores:
-| Field | Description |
-|-------|-------------|
-| `name` | Branch name |
-| `snapshot_id` | Associated snapshot ID |
-| `created_at` | ISO timestamp of creation |
-| `parent_branch` | Branch that was active when this branch was created |
-| `status` | Branch status (`active`) |
-## Managing Branches
-```
-# Show current branch and snapshot count
-python3 tools/session_snapshot.py status
-# List all branches
-python3 tools/session_snapshot.py branches
-# Switch to a branch (restores its snapshot)
-python3 tools/session_snapshot.py switch experiment
-# Create branch from specific snapshot
-python3 tools/session_snapshot.py branch my-branch --from 20260302_143000_baseline
-# Fork from a previous checkpoint
-python3 tools/session_snapshot.py fork --from 20260302_100000_pre-refactor --name "approach-b"
-# Preview a merge
-python3 tools/session_snapshot.py merge-preview experiment --into main
-# Apply a merge
-python3 tools/session_snapshot.py merge experiment --into main
-```
-## Feature Flag
-Branching is gated behind `OMG_BRANCHING_ENABLED` (default: `False`).
-Enable via environment variable:
-```bash
-export OMG_BRANCHING_ENABLED=true
-```
-Or in `settings.json`:
-```json
-{
-  "_omg": {
-    "features": {
-      "BRANCHING": true
-    }
-  }
-}
-```
-## Example Workflow
-```
-# 1. Create a baseline branch
-/OMG:session-branch --name "baseline"
-# 2. Do some experimental work...
-# 3. Create experiment branch to save progress
-/OMG:session-branch --name "experiment-auth"
-# 4. Switch back to baseline if experiment didn't work
-python3 tools/session_snapshot.py switch baseline
-```

package/build/lib/commands/OMG:session-fork.md DELETED Viewed

@@ -1,57 +0,0 @@
----
-description: "Fork OMG state from a specific snapshot checkpoint."
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: "--from <snapshot_id> --name <fork-name>"
----
-# /OMG:session-fork — Fork OMG State from Checkpoint
-Create a new branch from a specific snapshot checkpoint. This is a convenience wrapper around `/OMG:session-branch` that always requires a source snapshot.
-## Scope Statement
-**This command operates on `.omg/state/` only. It does NOT modify git history, workspace files, or conversation history.**
-## Important
-Forking is **OMG state only** — it restores a previous `.omg/state/` snapshot and creates a new named branch from it. It does **not** fork the conversation or create a parallel Claude session. Rollback restores OMG session state only, NOT git history or repo files.
-## Usage
-```
-/OMG:session-fork --from 20260302_143000_baseline --name "alt-approach"
-```
-## What It Does
-1. Looks up the specified snapshot by ID
-2. Restores that snapshot to `.omg/state/`
-3. Creates a new branch with the given name pointing to that snapshot
-4. Updates `.omg/state/current_branch.json`
-## When to Use Fork vs Branch
-| Action | Use Case |
-|--------|----------|
-| `/OMG:session-branch --name X` | Save current state as a named branch |
-| `/OMG:session-fork --from S --name X` | Go back to snapshot S and start a new exploration path |
-## Example
-```
-# List available snapshots to find a good fork point
-python3 tools/session_snapshot.py list
-# Fork from a previous checkpoint
-/OMG:session-fork --from 20260302_100000_pre-refactor --name "approach-b"
-# Continue working from that earlier state...
-```
-## Feature Flag
-Forking shares the `OMG_BRANCHING_ENABLED` feature flag with `/OMG:session-branch` (default: `False`).
-```bash
-export OMG_BRANCHING_ENABLED=true
-```

package/build/lib/commands/OMG:session-merge.md DELETED Viewed

@@ -1,138 +0,0 @@
----
-description: "Merge OMG state branches together with conflict detection."
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: "--from <source-branch> [--into <target-branch>] [--preview]"
----
-# /OMG:session-merge — Merge OMG State Branches
-Merge one OMG state branch into another with automatic conflict detection.
-## Scope Statement
-**This command operates on `.omg/state/` only. It does NOT modify git history, workspace files, or conversation history.**
-## Important
-Merging is **OMG state only** — it merges branch metadata (`.omg/state/branches/<name>.json`). It does **not** merge conversations, context windows, or file system state. Think of it as combining the tracked state from two named branches. Rollback restores OMG session state only, NOT git history or repo files.
-## Usage
-```
-/OMG:session-merge --from "experiment"
-/OMG:session-merge --from "experiment" --into "main"
-/OMG:session-merge --from "experiment" --preview
-```
-## What It Does
-1. Loads the source and target branch metadata as flat JSON dicts
-2. Detects conflicts (keys present in both branches with different values)
-3. If `--preview`: returns conflict report without applying changes
-4. If no conflicts: applies source changes on top of target (last-write-wins)
-5. Marks the source branch as `status: "merged"` in its metadata file
-6. Updates `.omg/state/current_branch.json` to the target branch
-## Conflict Detection
-A **value_conflict** occurs when both branches have the same key but different values. When conflicts are found, the merge is **aborted** — you must resolve conflicts manually before merging.
-Conflict report format:
-```json
-{
-  "key": "snapshot_id",
-  "source_value": "20260302_150000_experiment",
-  "target_value": "20260302_140000_main",
-  "conflict_type": "value_conflict"
-}
-```
-## Preview Mode
-Use `--preview` to see what a merge would do without applying changes:
-```
-python3 tools/session_snapshot.py merge-preview experiment --into main
-```
-Returns:
-```json
-{
-  "source": "experiment",
-  "target": "main",
-  "conflicts": [],
-  "changes": 2,
-  "preview": true
-}
-```
-## CLI Commands
-```
-# Merge source into target
-python3 tools/session_snapshot.py merge experiment --into main
-# Preview merge without applying
-python3 tools/session_snapshot.py merge-preview experiment --into main
-# Merge into default target (main)
-python3 tools/session_snapshot.py merge experiment
-```
-## Feature Flag
-Merging is gated behind `OMG_MERGE_ENABLED` (default: `False`).
-Enable via environment variable:
-```bash
-export OMG_MERGE_ENABLED=true
-```
-Or in `settings.json`:
-```json
-{
-  "_omg": {
-    "features": {
-      "MERGE": true
-    }
-  }
-}
-```
-## Merge Behavior
-| Scenario | Result |
-|----------|--------|
-| No conflicts | Source state overlaid on target (last-write-wins) |
-| Conflicts found | Merge aborted, conflicts returned |
-| Source branch missing | Error returned |
-| Target branch missing | Error returned |
-| Feature flag disabled | `{"skipped": true}` |
-## After Merge
-- The **target** branch is updated with merged state
-- The **source** branch status changes to `"merged"` (not deleted)
-- `current_branch.json` is updated to the target branch
-- Source branch remains accessible for reference
-## Example Workflow
-```
-# 1. Create branches
-/OMG:session-branch --name "main"
-/OMG:session-branch --name "experiment"
-# 2. Do experimental work on "experiment" branch...
-# 3. Preview the merge
-/OMG:session-merge --from "experiment" --preview
-# 4. If no conflicts, apply the merge
-/OMG:session-merge --from "experiment" --into "main"
-# 5. Verify merge
-python3 tools/session_snapshot.py branches
-```

package/build/lib/commands/OMG:setup.md DELETED Viewed

@@ -1,82 +0,0 @@
----
-description: "Native OMG setup and adoption flow for supported hosts"
-allowed-tools: Read, Write, Edit, Bash(python*:*), Bash(ls:*), Bash(grep:*)
-argument-hint: "[optional: --non-interactive, --mode omg-only|coexist, --preset safe|balanced|interop|labs|buffet|plugins-first]"
----
-# /OMG:setup
-Feature-gated: requires `OMG_SETUP_ENABLED=1` or `settings.json._omg.features.SETUP: true`.
-## Overview
-Native OMG setup for Claude Code, Codex, and other supported CLIs.
-The command keeps migration logic internal and focuses the user on a small adoption flow:
-1. Detect supported CLIs.
-2. Detect overlapping ecosystems.
-3. Recommend an adoption mode.
-4. Apply an OMG preset.
-5. Configure MCP and save preferences.
-Setup now runs foreign-plugin discovery in `interop` and `coexist` modes, reporting compatibility findings and potential overlaps.
-## Wizard Flow
-```text
-Step 1: Detect CLIs
-  - codex
-  - gemini
-  - kimi
-Step 2: Detect adoption context
-  - OMC-style markers
-  - OMX-style markers
-  - Superpowers-style markers
-Step 3: Choose mode
-  - OMG-only (recommended)
-  - coexist
-Step 4: Choose preset
-  - safe
-  - balanced
-  - interop
-  - labs
-  - buffet
-  - plugins-first (alias for interop)
-Step 5: Configure MCP and persist preferences
-  - writes .mcp.json
-  - writes .omg/state/cli-config.yaml
-  - writes .omg/state/adoption-report.json
-```
-## Modes
-`OMG-only`
-- Recommended default.
-- OMG becomes the main hooks, HUD, MCP, and orchestration layer.
-`coexist`
-- Advanced mode.
-- OMG avoids destructive overlap and keeps third-party command namespaces intact where possible.
-## Output
-The command emits a final summary that includes:
-- CLI detection results
-- auth status
-- MCP configuration status
-- selected preset
-- selected adoption mode
-- adoption report path
-## Public Path
-The public OMG journey is:
-1. install for your host
-2. run `/OMG:setup`
-3. run `/OMG:crazy <goal>`

package/build/lib/commands/OMG:stats.md DELETED Viewed

@@ -1,225 +0,0 @@
----
-description: "Display session analytics, tool usage trends, file heatmaps, and failure patterns."
-allowed-tools: Read, Bash(python*:*), Grep
-argument-hint: "[weekly|files|failures|dashboard]"
----
-# /OMG:stats — Session Analytics
-Display session analytics, tool usage trends, file heatmaps, and failure patterns.
-## Usage
-```
-/OMG:stats
-/OMG:stats weekly
-/OMG:stats files
-/OMG:stats failures
-/OMG:stats dashboard
-```
-## Sub-Commands
-### `/OMG:stats` (default)
-Show current session summary: duration, tool calls, success rate, cost, and test runs.
-```python
-from hooks.query import get_session_summary
-summary = get_session_summary(".")
-duration_m = summary["duration"] // 60
-duration_s = summary["duration"] % 60
-print(f"Duration:       {duration_m}m {duration_s}s")
-print(f"Tool calls:     {summary['tool_calls']}")
-print(f"Success rate:   {summary['success_rate']:.1%}")
-print(f"Files modified: {summary['files_modified']}")
-print(f"Tests run:      {summary['tests_run']}")
-print(f"Tokens used:    {summary['tokens_used']:,}")
-print(f"Cost:           ${summary['cost_usd']:.4f}")
-```
-### `/OMG:stats weekly`
-Show last 7 days trend analysis by aggregating tool stats and escalation effectiveness.
-```python
-from hooks.query import get_tool_stats, get_escalation_effectiveness
-tools = get_tool_stats(".")
-escalations = get_escalation_effectiveness(".")
-# Per-tool breakdown
-for tool, stats in sorted(tools.items(), key=lambda x: x[1]["count"], reverse=True):
-    print(f"  {tool}: {stats['count']} calls, {stats['success_rate']:.0%} success, {stats['avg_tokens']:.0f} avg tokens")
-# Escalation summary
-print(f"\nEscalations: {escalations['escalations']} total, {escalations['resolved']} resolved, {escalations['unresolved']} unresolved")
-```
-### `/OMG:stats files`
-Show file-level heatmap of the most read, written, and edited files.
-```python
-from hooks.query import get_file_heatmap
-heatmap = get_file_heatmap(".")
-# Sort by total interactions (reads + writes + edits)
-ranked = sorted(
-    heatmap.items(),
-    key=lambda x: x[1]["reads"] + x[1]["writes"] + x[1]["edits"],
-    reverse=True,
-)
-print(f"{'File':<50} {'Reads':>6} {'Writes':>7} {'Edits':>6}")
-print("-" * 73)
-for path, counts in ranked[:20]:
-    total = counts["reads"] + counts["writes"] + counts["edits"]
-    print(f"{path:<50} {counts['reads']:>6} {counts['writes']:>7} {counts['edits']:>6}")
-```
-### `/OMG:stats failures`
-Show top failure patterns and their resolution status.
-```python
-from hooks.query import get_failure_hotspots, get_escalation_effectiveness
-hotspots = get_failure_hotspots(".")
-escalations = get_escalation_effectiveness(".")
-for pattern, details in sorted(hotspots.items(), key=lambda x: x[1]["count"], reverse=True):
-    status = "ESCALATED" if details["escalated"] else "active"
-    print(f"  [{status}] {pattern}: {details['count']} failures")
-    for err in details["last_3_errors"]:
-        print(f"    - {err[:100]}")
-print(f"\nResolution: {escalations['resolved']}/{escalations['escalations']} escalations resolved")
-```
-### `/OMG:stats dashboard`
-Generate a self-contained HTML dashboard at `.omg/state/dashboard.html`.
-The dashboard includes:
-- Session summary cards (duration, tool calls, cost, success rate)
-- Tool usage bar chart (via CDN Chart.js)
-- File heatmap table (top 20 files by interaction count)
-- Failure pattern list with escalation status
-```python
-import json
-import os
-from hooks.query import (
-    get_session_summary,
-    get_tool_stats,
-    get_file_heatmap,
-    get_failure_hotspots,
-)
-summary = get_session_summary(".")
-tools = get_tool_stats(".")
-heatmap = get_file_heatmap(".")
-failures = get_failure_hotspots(".")
-dashboard_data = {
-    "summary": summary,
-    "tools": tools,
-    "heatmap": dict(sorted(
-        heatmap.items(),
-        key=lambda x: x[1]["reads"] + x[1]["writes"] + x[1]["edits"],
-        reverse=True,
-    )[:20]),
-    "failures": failures,
-}
-# Write self-contained HTML with embedded Chart.js
-output_path = os.path.join(".omg", "state", "dashboard.html")
-os.makedirs(os.path.dirname(output_path), exist_ok=True)
-# ... (HTML template with CDN Chart.js and embedded JSON data)
-print(f"Dashboard written to {output_path}")
-```
-## Feature Flag
-- **Flag name**: `OMG_SESSION_ANALYTICS_ENABLED`
-- **Default**: `False` (disabled)
-- **Enable**: `export OMG_SESSION_ANALYTICS_ENABLED=1`
-Or set in `settings.json`:
-```json
-{
-  "_omg": {
-    "features": {
-      "SESSION_ANALYTICS": true
-    }
-  }
-}
-```
-## Output Example
-```
-============================================================
-  OMG Session Analytics — Summary
-============================================================
-  Duration:       23m 47s
-  Tool calls:     142
-  Success rate:   94.4%
-  Files modified: 18
-  Tests run:      6
-  Tokens used:    287,450
-  Cost:           $1.1142
-  Top Tools:
-    Bash:           58 calls, 95% success, 1,240 avg tokens
-    Read:           34 calls, 100% success, 890 avg tokens
-    Edit:           22 calls, 91% success, 1,100 avg tokens
-    Write:          16 calls, 100% success, 950 avg tokens
-    Grep:           12 calls, 100% success, 320 avg tokens
-  Failure Hotspots:
-    [ESCALATED] hooks/budget_governor.py: 4 failures
-    [active] tests/test_integration.py: 2 failures
-  Escalations: 1 total, 0 resolved, 1 unresolved
-============================================================
-```
-## Safety
-- **Read-only**: All sub-commands only read from existing ledger/tracker files
-- **Feature-gated**: Requires `SESSION_ANALYTICS` flag enabled
-- **No mutations**: Never modifies ledger data, failure tracker, or working memory
-- **Crash-isolated**: All query operations exit 0 on failure (via query.py internals)
-- **Dashboard**: Writes only to `.omg/state/dashboard.html` (inside managed state directory)
-## API
-```python
-from hooks.query import (
-    get_session_summary,
-    get_tool_stats,
-    get_failure_hotspots,
-    get_escalation_effectiveness,
-    get_file_heatmap,
-)
-# Current session summary
-summary = get_session_summary(".")
-# Per-tool statistics
-tools = get_tool_stats(".")
-# Failure patterns and escalation status
-failures = get_failure_hotspots(".")
-escalations = get_escalation_effectiveness(".")
-# File interaction heatmap
-heatmap = get_file_heatmap(".")
-```

package/build/lib/commands/OMG:teams.md DELETED Viewed

@@ -1,54 +0,0 @@
----
-description: OMG internal staged team routing (standalone). /OMG:team canonical, /OMG:teams compatibility alias.
-allowed-tools: Read, Grep, Glob, Bash(git:*), Bash(rg:*), Bash(find:*), Bash(cat:*), Bash(python3:*)
-argument-hint: "[codex|gemini|ccg|auto] 'problem statement'"
----
-# /OMG:teams — Standalone Internal Router
-Canonical alias: `/OMG:team`
-Compatibility alias: `/OMG:teams`
-Use OMG's internal router using internal routing.
-## Input contract
-- target: `auto|codex|gemini|ccg`
-- problem: clear issue statement
-- context: optional constraints
-- files: optional focus paths
-- expected_outcome: optional acceptance target
-## Execution
-Use internal CLI router (canonical):
-```bash
-OMG_CLI="${OMG_CLI_PATH:-$HOME/.claude/omg-runtime/scripts/omg.py}"
-if [ ! -f "$OMG_CLI" ] && [ -f "scripts/omg.py" ]; then OMG_CLI="scripts/omg.py"; fi
-python3 "$OMG_CLI" team --target auto --problem "[problem]"
-```
-Compatibility alias (legacy):
-```bash
-python3 "$OMG_CLI" teams --target auto --problem "[problem]"
-```
-For explicit target:
-```bash
-python3 "$OMG_CLI" team --target codex --problem "[problem]"
-```
-## Staged flow
-- `team-plan`: resolve context packet and clarification/council gate before dispatch
-- `team-exec`: launch workers only when context is resolved
-- `team-verify`: run verification and critic synthesis
-- `team-fix`: surface blockers/next actions for follow-up iteration
-## Output schema
-`TeamDispatchResult { status, findings[], actions[], evidence{} }`
-## Full-power sub-agent protocol
-- For non-trivial tasks, launch multiple sub-agents in parallel (`run_in_background=true`) for independent tracks.
-- Collect all task outputs before responding (`background_output` per task id).
-- Run a `sequential-thinking` merge step to produce one dependency-ordered execution plan.