get-unpublished-changes
SkillAI & modelsThis skill lets your AI compare your current code against the latest versions you have published to npm and see exactly what has not shipped yet. Once added, your AI can list all unpublished changes grouped by release layer and draft release notes from them. It gives you a quick, reliable answer to what changed since your last release.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, ask your AI something like what's unpublished or what changed since the last release. It will compare your code against your published npm versions and summarize the differences by layer.
Then ask your AI: use the get-unpublished-changes skill
What your AI can do with it
- Compare your current code with the latest published npm versions
- List every change that has not been published yet
- Group unpublished changes by release layer
- Draft release notes from the unpublished changes
- Answer questions like what changed or what's new since the last release
What this skill tells your AI
The instructions your AI receives, as published by code-yeongyu/oh-my-openagent in .agents/skills/get-unpublished-changes/SKILL.md and read by ahel’s review.
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, andlazycodex-ai. - Run
git diff v{published-version}..HEADto 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 foromo pure components,omo opencode,omo codexLayer-specific Version Recommendation: patch/minor/major per layer plus one overall release bump
Signals
- GitHub stars
- 69k
- Forks
- 6k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
get-unpublished-changes- Source
- github.com/code-yeongyu/oh-my-openagent