Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Compares HEAD with the latest published npm versions and describes unpublished changes by release layer, with version bump recommendations per layer.
Install Unpublished Changes by Release Layer
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .claude/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .claude/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .agents/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .agents/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .cursor/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .cursor/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/code-yeongyu/oh-my-openagent.git --path .agents/skills/get-unpublished-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .gemini/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .gemini/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .github/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .github/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install code-yeongyu/oh-my-openagent get-unpublished-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/get-unpublished-changes .opencode/skills/get-unpublished-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "get-unpublished-changes" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes into .opencode/skills/get-unpublished-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "get-unpublished-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
get-unpublished-changes- GitHub stars
- 70k
- Token cost
- ~587 tokens
- SKILL.md length
- 282 words
- Files
- 1
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Compares HEAD with the latest published npm versions and describes unpublished changes by release layer, with version bump recommendations per layer.
- Works in 3 steps: Read the actual diff to understand WHAT… → Describe the REAL change in plain language → Explain WHY it matters (if not obvious)
- Preparing release notes for the npm packages
- SKILL.md covers CRITICAL: DO NOT just copy…, Release Layers, Steps: and Output Format:
- Calls git
What it does
Finds out what has changed since the last npm release of oh-my-opencode, oh-my-openagent and lazycodex-ai, then reports it against three release layers: omo pure components, omo opencode and omo codex. It detects the latest published versions, runs git diff from the published tag to HEAD, and sorts every file into one or more layers before grouping by feat, fix, refactor or docs.
Commit messages must not be copied. For each commit the skill reads the real diff and describes what changed in plain language and why it matters. The output includes a Layered Impact Matrix, breaking changes by layer, and a version recommendation per layer plus one overall bump. Paths matching senpi, omo-senpi, senpi-task, pi-goal or pi-webfetch go into a separate internal exclusion ledger, and the analysis is delivered immediately with no questions.
When your agent uses it
- Preparing release notes for the npm packages
- Deciding patch, minor or major per package layer
- Seeing what changed since the last published version
- Checking which layers a breaking change affects
Example prompts
- “What changed since the last published oh-my-opencode version?”
- “List the unpublished changes by release layer and recommend version bumps.”
- “What's new since the last npm release? Keep the senpi adapters out of it.”
Requirements
- Git history with the published version tags
- Network access to read the latest npm versions
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read the actual diff to understand WHAT CHANGED
- Describe the REAL change in plain language
- Explain WHY it matters (if not obvious)
What it can do on your machine
Read from SKILL.md and the folder at commit cbd7dd2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Unpublished Changes by Release Layer loads about 587 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 282 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 282 words (~587 tokens).
“IMMEDIATELY output the analysis. NO questions. NO preamble.”
- name
- get-unpublished-changes
Files
Just SKILL.md in .agents/skills/get-unpublished-changes of code-yeongyu/oh-my-openagent.
Open the folder on GitHubat commit cbd7dd2
Compare with similar skills
Unpublished Changes by Release Layer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Unpublished Changes by Release Layer this skillcode-yeongyu/oh-my-openagent | 70k | — | ~587 | Automated safety check: Pass | Custom licence | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Git Changes ReporterNo-Trade-No-Life/Yuan | 352 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
More from code-yeongyu/oh-my-openagent
All 44 skills in this repoast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Browser Control with Omowright
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
LSP Setup
code-yeongyu/oh-my-openagent
Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
Related
Categories
Questions about Unpublished Changes by Release Layer
What does Unpublished Changes by Release Layer do?
Compares HEAD with the latest published npm versions and describes unpublished changes by release layer, with version bump recommendations per layer. Finds out what has changed since the last npm release of oh-my-opencode, oh-my-openagent and lazycodex-ai, then reports it against three release layers: omo pure components, omo opencode and omo codex. It detects the latest published versions, runs git diff from the published tag to HEAD, and sorts every file into one or more layers before grouping by feat, fix, refactor or docs.
When should I use Unpublished Changes by Release Layer?
Unpublished Changes by Release Layer fits situations like: preparing release notes for the npm packages; deciding patch, minor or major per package layer; seeing what changed since the last published version; checking which layers a breaking change affects.
How do I install Unpublished Changes by Release Layer in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a claude-code`. Or copy the skill folder (.agents/skills/get-unpublished-changes in code-yeongyu/oh-my-openagent) into .claude/skills/get-unpublished-changes in your project. Claude Code loads it when a task matches its description.
How do I install Unpublished Changes by Release Layer in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a codex`. Or copy the skill folder (.agents/skills/get-unpublished-changes in code-yeongyu/oh-my-openagent) into .agents/skills/get-unpublished-changes in your project. Codex loads it when a task matches its description.
Can I use Unpublished Changes by Release Layer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill get-unpublished-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/get-unpublished-changes, .gemini/skills/get-unpublished-changes, .github/skills/get-unpublished-changes and .opencode/skills/get-unpublished-changes in your project.
What does Unpublished Changes by Release Layer need to run?
Going by SKILL.md and its folder, Unpublished Changes by Release Layer needs the command-line tools its instructions call (git). Our summary lists: Git history with the published version tags; Network access to read the latest npm versions.
Does Unpublished Changes by Release Layer access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Unpublished Changes by Release Layer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Unpublished Changes by Release Layer use?
Unpublished Changes by Release Layer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Unpublished Changes by Release Layer use?
About 587 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Unpublished Changes by Release Layer?
Skills that share tags, products or a category with Unpublished Changes by Release Layer: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Unpublished Changes by Release Layer?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,850 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 7, 2026.
Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.