skills.rest
neogenz
neogenzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-changelog

Generate a unified product changelog from git history across multiple packages.

4|Updated Jun 25, 2025
Search Tags:#automation#git#workflow#changelog#release#changesets
One-click install
npx skills add https://github.com/neogenz/pulpe --skill update-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/neogenz/pulpe/tree/main/.claude/skills/update-changelog
Command: npx skills add https://github.com/neogenz/pulpe --skill update-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates release management by consolidating changes across multiple packages into a single product version and changelog, ensuring consistent and auditable deployments.

Core Features & Use Cases

  • Analyze changes since the last tag or main to determine impact across frontend, backend, shared, and other packages.
  • Generate a cohesive release changelog and a single product tag for the release.
  • Prompt for explicit user approval before applying version bumps, pushing changes, or creating GitHub releases.
  • Integrate with changesets and iOS alignment rules to keep all platforms in sync.

Quick Start

  1. Say "update changelog" or "release" to invoke the process.
  2. Review the proposed version and changelog, then approve or adjust.
  3. Follow the prompts to commit, tag, and publish the GitHub release after confirmation.

Frequently Asked Questions about update-changelog

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

FAQPage Schema
How do I generate a single changelog for multiple packages from git history?▼

To generate a unified changelog from git history, this Skill analyzes changes since your last tag or main branch to consolidate impacts across frontend, backend, and shared packages into one cohesive product version release.

How do I automate release management across multiple platforms while keeping versions in sync?▼

Automating release management across platforms is achieved by proposing a unified version bump plan and enforcing iOS alignment rules and Changesets integration to keep all platforms synchronized before pushing.

Can I review and approve version bumps before changes are pushed to GitHub?▼

Yes, you can review version bumps before pushing because the workflow enforces safety rules that prompt for explicit user approval before applying any version changes, committing tags, or creating GitHub releases.

What's the best way to consolidate changesets across frontend and backend packages into one product tag?▼

The best way to consolidate changesets into one product tag is to analyze cross-package impacts from git history, generate a cohesive changelog, and prompt for confirmation to commit and tag the unified release.

Does this changelog automation tool work with Changesets and iOS alignment rules?▼

Yes, this changelog automation works with Changesets and iOS alignment rules to keep all platforms in sync, analyzing git history to propose release plans that enforce consistent and auditable deployments.

Related Skills

Explore More Software Engineering Skills→
kurokeitakurokeita
1

changelog-automation

Automate changelog generation from commits, PRs, and releases.

Community
Intermediate
mazenyassergithubmazenyassergithub
6

release

Automate software releases with version bumping, tests, Git tags, npm publishing, and GitHub releases.

Community
Advanced
Fl2vioFl2vio
1

github-release-management

Orchestrate GitHub release workflows across planning, validation, packaging, and publishing.

Community
Advanced
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate