skills.rest
PyModel
PyModelOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sync-changelog

Syncs the CLI package changelog into the docs-site changelog and opens a PR.

18|8|Updated Jun 17, 2026
Search Tags:#changelog#versioning#documentation#pull request#git workflow#release notes#changesets
One-click install
npx skills add https://github.com/PyModel/pythinker-code --skill sync-changelog-pymodel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-changelog
Source: https://github.com/PyModel/pythinker-code/tree/main/.agents/skills/sync-changelog
Command: npx skills add https://github.com/PyModel/pythinker-code --skill sync-changelog-pymodel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After each release, the user-facing docs changelog falls behind the changesets-generated package changelog, and manually copying, cleaning, and classifying entries is error-prone and inconsistent. ## Core Features & Use Cases - Changelog Synchronization: Copies new version blocks from apps/pythinker-code/CHANGELOG.md into docs/release-notes/changelog.md, stripping PR links, commit hashes, and Thanks credits. - Entry Curation and Classification: Merges low-signal entries into catch-all lines and classifies entries into Features, Polish, Bug Fixes, Refactors, or Other sections. - Safe Release Workflow: Works on a dedicated docs/changelog-sync-* branch, runs a human review checkpoint, verifies with the docs build, and opens a PR via gh. - Use Case: After version 0.2.1 is published to npm, run this Skill to sync its changelog entries into the docs site, review the diff, and open a properly formatted PR. ## Quick Start Sync the newly published CLI release changelog into the docs release notes and open a PR for it.

Frequently Asked Questions about sync-changelog

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

FAQPage Schema
How do I sync a package changelog into a docs site after release?▼

Run this Skill after the Release PR is merged and npm publish succeeds. It copies new version blocks from apps/pythinker-code/CHANGELOG.md into docs/release-notes/changelog.md, strips decorations, classifies entries, and opens a PR on a docs/changelog-sync-* branch.

When should the changelog sync run in the release process?▼

Run it only after the Release PR is merged, Version Packages has completed, and the new version is published to npm. Running it earlier fails because changesets has not yet written the new version into the upstream changelog.

How are changelog entries classified into sections?▼

Entries are classified from stripped text into Features, Polish, Bug Fixes, Refactors, or Other using keyword hints and, when unclear, by inspecting the commit with git show or the PR with gh pr view. Low-signal entries fold into a single catch-all line.

Can I commit the changelog sync directly to main?▼

No. All sync work happens on a dedicated docs/changelog-sync-<version> branch, and a PR is opened with gh pr create. The Skill also enforces a human review checkpoint before committing or pushing.

What happens to PR links and Thanks credits during sync?▼

They are stripped every time. Only the entry body text is kept, along with version headings and release dates taken from the published GitHub Release tag.

Related Skills

Explore More Software Engineering Skills→
firstsun-devfirstsun-dev
3

release-openspec

Audits, prepares, publishes, and finalizes OpenSpec releases via GitHub and Changesets.

Official
Advanced
jMertajMerta
130

release-notes

Generate Markdown release notes from git history and merged PRs.

Community
Basic
saleorsaleor
29

creating-changesets

Automate Changesets semantic versioning workflows in Node.js monorepos with Git and PNPM.

Official
Advanced
bmad-code-orgbmad-code-org
51.7k

bmad-os-release-module

Automates npm release process including changelog drafting, versioning, git tagging, publishing, and GitHub releases.

Official
Advanced