skills.rest
hsch14
hsch14COMMUNITY
Explore all skills by this author →
GitHub

get-unpublished-changes

Compare git HEAD against published npm versions to categorize unpublished changes.

Updated Jul 16, 2026
Search Tags:#automation#git#changelog#npm#release#semver
One-click install
npx skills add https://github.com/hsch14/ABC-car_insurance --skill get-unpublished-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: get-unpublished-changes
Source: https://github.com/hsch14/ABC-car_insurance/tree/main/.agents/skills/get-unpublished-changes
Command: npx skills add https://github.com/hsch14/ABC-car_insurance --skill get-unpublished-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the difficulty of tracking unreleased code changes across complex, multi-package repositories, ensuring that version bumps and release notes are accurate and layer-specific.

Core Features & Use Cases

  • Automated Diff Analysis: Compares the current HEAD against the latest published npm versions to identify actual code changes.
  • Layered Impact Assessment: Categorizes changes into specific release layers (pure components, opencode, codex) to determine appropriate semver bumps.
  • Use Case: Use this before a release to generate a structured changelog that identifies which packages need updates and whether a patch, minor, or major version bump is required for each layer.

Quick Start

Ask the agent to analyze the unpublished changes and provide a release recommendation for the current repository.

Frequently Asked Questions about get-unpublished-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from unpublished git commits?▼

Yes, you can automate semver version bump recommendations by analyzing feat, fix, and refactor commits. The Skill evaluates unpublished changes across defined release layers and suggests the appropriate patch, minor, or major version bump for each package.

What is the best way to track unreleased changes in a multi-package npm repository?▼

Tracking unreleased changes in a multi-package npm repository is done by comparing the current git HEAD against the latest published npm versions. This categorizes code changes into specific release layers to ensure accurate version bumps and layer-specific changelogs.

How do I categorize npm package changes by release layer before publishing?▼

You can categorize npm package changes by assessing impact across defined release layers such as core components, opencode infrastructure, and codex plugins. This categorization determines the appropriate semver bump required for each specific layer.

Does this changelog automation work with standard git commit types?▼

Yes, this changelog automation works with standard git commit types. It specifically detects feat, fix, and refactor commits to generate structured release notes and semver recommendations based on the actual code changes found.

Can I analyze release impact for core components and infrastructure separately?▼

Yes, you can analyze release impact separately. The Skill evaluates changes across defined release layers including core components, opencode infrastructure, and codex plugins, generating layer-specific release notes and semver recommendations.

Related Skills

Explore More Software Engineering Skills→
hckhanhhckhanh
3

ctx-upgrade

Fetch, build, install, and configure the Context Mode plugin automatically.

Community
Intermediate
OliverOuyangOliverOuyang
1

release

Automate version bumps, tests, git tags, npm publish, and GitHub releases for oh-my-claudecode.

Community
Advanced
SirPedrSirPedr

conventional-commit

Generate Conventional Commits messages with type, scope, subject, body, and footer.

Community
Basic
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced