SkillAgentSearch skills...

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.

Install / Use

npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of get-unpublished-changes

get-unpublished-changes scores 90/100 on our quality scale, 196th of 1,630 Development & Engineering skills we index (top 13%).

Its SKILL.md is 2.3 KB long, split into 4 sections and no code examples: moderately detailed.

With 69,362 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
20/30
Structure
8/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so get-unpublished-changes is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

get-unpublished-changes compared with similar skills

All 4 of these similar skills score higher than get-unpublished-changes; compare them before choosing.

SkillScoreStarsUpdatedFormat
get-unpublished-changes (this skill)by code-yeongyu9069.4ktodaySKILL.md
ai-job-searchby MadsLorentzen10043.9k3d agoCLAUDE.md
claude-howtoby luongnv8910041.7k5d agoCLAUDE.md
algorithmic-artby anthropics100177.9k2d agoSKILL.md
pptxby anthropics100177.9k2d agoSKILL.md

Frequently asked questions

How do I install get-unpublished-changes?
Run npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes. The install tabs above show the steps for each supported agent.
Which AI agents does get-unpublished-changes work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is get-unpublished-changes safe to use?
It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is get-unpublished-changes still maintained?
The repository was last updated today, so get-unpublished-changes is actively maintained.

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

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:

| 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:

  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

Related Skills

View on GitHub
GitHub Stars69.4k
CategoryDevelopment
Updated16h ago
Forks5.7k

Languages

TypeScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium