Get unpublished changes

Skill code-yeongyu/oh-my-openagent/.agents/skills/get-unpublished-changes

omo/lazycodex: The coding agent for tokenmaxxers;the one and only agent harness for complex codebases. For your Codex, for your OpenCode

Install

npx -y skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

SKILL.md

2.3 KB, 539 tokens by cl100k_base, as published. Nobody here has run it

IMMEDIATELY output the analysis. NO questions. NO preamble.

CRITICAL: DO NOT just copy commit messages!

For each commit, you MUST:

Read the actual diff to understand WHAT CHANGED
Describe the REAL change in plain language
Explain WHY it matters (if not obvious)

Release Layers

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.

Steps:

Detect latest published versions for oh-my-opencode, oh-my-openagent, and lazycodex-ai.
Run git diff v{published-version}..HEAD to see actual changes.
Classify every file into one or more release layers before grouping by feat/fix/refactor/docs.
Describe the REAL changes and why each layer cares.
Note breaking changes by affected layer.
Recommend a layer-specific version bump and one overall workflow bump.

Output Format:

feat: "Added X that does Y" (not just "add X feature")
fix: "Fixed bug where X happened, now Y" (not just "fix X bug")
refactor: "Changed X from A to B, now supports C" (not just "rename X")

Include:

Layered Impact Matrix: rows for omo pure components, omo opencode, omo codex
Layer-specific Version Recommendation: patch/minor/major per layer plus one overall release bump