Get Unpublished Changes

by code-yeongyuf9181a90b5e2No license69K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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

Instructions onlySoftware Development Productivity & Workflow

AI-generated overview

Compares HEAD with the latest published npm versions and lists unpublished changes by release layer.

What it does: This skill inspects the git diff between the latest published npm versions of oh-my-opencode, oh-my-openagent, and lazycodex-ai and the current HEAD. It classifies changed files into three release layers (omo pure components, omo opencode, omo codex), describes the real changes in plain language, and flags breaking changes. It produces a layered impact matrix and layer-specific version bump recommendations plus one overall release bump, excluding certain internal-adapter paths into a separate ledger.
When to use it: Use it when preparing a release or changelog and you need to know what has changed since the last published npm versions. It fits questions like what changed, what is new, or which semver bump each package needs.
Requirements: Requires access to the repository's git history and the ability to run git diff against published version tags, plus network or registry access to detect the latest published npm versions of the named packages. It ships no scripts; it is instructions only.

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

Source and attribution

Source:code-yeongyu/oh-my-openagentin.agents/skills/get-unpublished-changesat commitf9181a9

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Get Unpublished Changes

CRITICAL: DO NOT just copy commit messages!

Release Layers

Steps:

Output Format:

Source and attribution

More from code-yeongyu/oh-my-openagent

Work With Pr

Remove Deadcode

Security Research

Publish

Pre Publish Review

Github Triage

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices