Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Unpublished Changes · code-yeongyu | DecimalAI

devopsby code-yeongyu

Get Unpublished Changes

code-yeongyu/get-unpublished-changes

Source code-yeongyu/oh-my-openagent ↗License NOASSERTION

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

SkillScore82Maintained

Automatic

DevOps & SRE pack

Last verified 8/7/2026

What it changes

Passed 18 of 22 test cases with the skill, and 8 of 22 without it.

Without skill36%

With skill82%

Checks it passed that the model alone missed

The response includes a section titled Layered Impact Matrix.
The response contains no questions or requests for user input.
The response excludes senpi paths from user-facing release notes.

and 16 more in the full report

13 fixed5 passed either way1 still failing3 broke

Pass-rate lift: +45 pp
Tokens: +25%
Agent turns: 0%
Response time: -12%

Model gemini-3.6-flashMeasured 8/7/2026v118 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/code-yeongyu-get-unpublished-changes/SKILL.md https://app.decimal.ai/s/code-yeongyu-get-unpublished-changes/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add code-yeongyu-get-unpublished-changes, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/code-yeongyu-get-unpublished-changes/ and pins it in .decimal/skills.lock

decimalai skills add code-yeongyu-get-unpublished-changes

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/code-yeongyu-get-unpublished-changes/SKILL.md https://app.decimal.ai/s/code-yeongyu-get-unpublished-changes/SKILL.md

Raw file: /s/code-yeongyu-get-unpublished-changes/SKILL.md ↗ · machine-readable summary at /s/code-yeongyu-get-unpublished-changes.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 13

Prompt

A bug fix in packages/core/auth.ts prevented token refresh timeouts. Provide the exact formatted line item for this fix in the release notes.

What was checked, without and with the skill
Checked	Without skill	With skill
The fix description follows the pattern fix: Fixed bug where X happened, now Y.	Missed	Passed

case-11 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md37 linessingle file

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

Track record

Benchmark

18 / 22

test cases passed, vs 8 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

code-yeongyu / oh-my-openagent

.agents/skills/get-unpublished-changes/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.