mcpbeat

Get Unpublished Changes

code-yeongyu/get-unpublished-changes

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

586 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
67138
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill get-unpublished-changes

What it tells the agent to use

found in the instruction text
WebFetch fetches pages from the network

The instruction itself

4 sections, as written by the author

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

How to use it

Copy the folder

Take code-yeongyu/get-unpublished-changes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.