How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill get-unpublished-changesBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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





