Compare current code with the latest published npm releases to identify unpublished changes. Read actual code differences, explain their impact across shared components and agent environments, and recommend version updates for each release layer.
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
Review the instructions the agent will receive before you install.
IMMEDIATELY output the analysis. NO questions. NO preamble.
For each commit, you MUST:
Analyze every change against these exact layers:
| Layer | Includes | Version question |
|---|---|---|
omo pure components | packages/*-core, MCP packages, packages/shared-skills, reusable scripts | Do shared components need a patch/minor/major release note even if adapters only consume them internally? |
omo opencode | Root oh-my-opencode / oh-my-openagent, src/, .opencode/, .agents/, CLI, config, hooks, tools, docs | What semver bump should the OpenCode/OpenAgent npm packages use? |
omo codex | packages/omo-codex, lazycodex-ai, Codex plugin metadata/hooks, bundled MCP runtimes, code-yeongyu/lazycodex marketplace payload | Does LazyCodex need the same bump, a Codex-only note, or a marketplace release? |
Exclude commits and paths matching senpi, omo-senpi, senpi-task, pi-goal, or pi-webfetch from user-facing notes and version recommendations. Record them only in a separate internal-adapter exclusion ledger.
oh-my-opencode, oh-my-openagent, and lazycodex-ai.git diff v{published-version}..HEAD to see actual changes.Include:
Layered Impact Matrix: rows for omo pure components, omo opencode, omo codexLayer-specific Version Recommendation: patch/minor/major per layer plus one overall release bumpNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Finds and rewrites code by its syntax structure across 25 languages. Use it to locate matching calls or declarations, preview bulk changes, and run reusable YAML rules that check code or apply fixes.
Automate forms, clicks, screenshots, and website checks in a browser where you are already signed in. A separately launched browser also supports scraping and network capture, while login or verification steps can be handed to a person.
Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.
Search local session histories across Codex, Claude Code, OpenCode, and other coding agents. Find earlier requests, inspect transcripts and child sessions, and reconstruct past work using recorded evidence, with filters for dates, projects, platforms, and models.
Help Codex respond to automatic warnings about comments after code edits. It explains when the checker runs and directs Codex to fix the flagged comment or explain it before continuing with other work.
Saves multi-agent workflows as named JSON files and runs them again without copying their definitions. Handles placeholders and run keys so repeated workflows can create fresh runs or deliberately reuse an existing run.