Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-09 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 18% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 120% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 51% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 35% | 0% |
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 bumpOther measured skills in the registry, with their headline benchmark lift.