mcpField
G
get-unpublished-changes

get-unpublished-changes

github.com/code-yeongyuDevelopment70.4k486 installsUpdated today
Repository

About get-unpublished-changes

A release-analysis skill that reviews unpublished changes across Oh My OpenCode and LazyCodex release layers. It reads diffs, classifies impact, and recommends layer-specific and overall version bumps.

Key features

  1. 01Detects published package versions
  2. 02Analyzes diffs against published releases
  3. 03Classifies changes by release layer
  4. 04Explains changes and their impact
  5. 05Recommends layer and overall version bumps

Use cases

  1. 01Preparing release notes from unpublished commits
  2. 02Assessing version bumps for OpenCode and Codex packages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill get-unpublished-changes

After installing, type/get-unpublished-changesin Claude Code to confirm it loaded.

Details

From the project README

IMMEDIATELY output the analysis. NO questions. NO preamble.

CRITICAL: DO NOT just copy commit messages!

For each commit, you MUST:

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

Release Layers

Analyze every change against these exact layers:

LayerIncludesVersion question
omo pure componentspackages/*-core, MCP packages, packages/shared-skills, reusable scriptsDo shared components need a patch/minor/major release note even if adapters only consume them internally?
omo opencodeRoot oh-my-opencode / oh-my-openagent, src/, .opencode/, .agents/, CLI, config, hooks, tools, docsWhat semver bump should the OpenCode/OpenAgent npm packages use?
omo codexpackages/omo-codex, lazycodex-ai, Codex plugin metadata/hooks, bundled MCP runtimes, code-yeongyu/lazycodex marketplace payloadDoes 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:

  1. Detect latest published versions for oh-my-opencode, oh-my-openagent, and lazycodex-ai.
  2. Run git diff v{published-version}..HEAD to see actual changes.
  3. Classify every file into one or more release layers before grouping by feat/fix/refactor/docs.
  4. Describe the REAL changes and why each layer cares.
  5. Note breaking changes by affected layer.
  6. 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

Comments

Markdown supported