TypingMindTypingMindThe best frontend for AI
Get Unpublished Changes logo

Get Unpublished Changes

CommunityPopular
code-yeongyu
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.

Overview

Publishercode-yeongyu
Repositoryoh-my-openagent
Skill nameget-unpublished-changes
Stars
70K
Forks
5.7K
Bundled files
Instructions only
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by code-yeongyu on GitHub. Read the source before you install it.

Installation

Install the Get Unpublished Changes AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent
mkdir -p .claude/skills
cp -r /tmp/oh-my-openagent/.agents/skills/get-unpublished-changes .claude/skills/get-unpublished-changes
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Get Unpublished Changes in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Get Unpublished Changes on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Get Unpublished Changes is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Get Unpublished Changes AI skill do?

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

Why use Get Unpublished Changes on TypingMind?

Because you install it once and use it with any model. Get Unpublished Changes is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Get Unpublished Changes in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/get-unpublished-changes. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Get Unpublished Changes?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Get Unpublished Changes?

As many as you like. As long as a model supports skills, you can use Get Unpublished Changes with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Get Unpublished Changes AI skill free?

It is published on GitHub by code-yeongyu. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Live Updater

openclaw
OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

82.2K
391K
2 files
View
openclaw logo

Openclaw Pr Maintainer

openclaw
OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

82.2K
391K
5 files
View
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇