Sync Changelog Across Repos: A Release-Hygiene Skill for AI Agents

Where this fits

You just merged the Release PR, the Version Packages workflow finished, and npm shows your CLI package at v1.4.2. Now your docs site still lists v1.4.1 in both English and Chinese changelogs. Manually copying the new entries, translating them, and opening a PR on a separate branch is exactly the kind of repetitive, error-prone task that slows down maintainers. The sync-changelog skill lets an agent take over that entire flow—reading the authoritative changelog, updating both locale files, and opening a clean PR—so you can move on to feature work.

Why agents benefit

• Single-source extraction: The agent knows that apps/nori-code/CHANGELOG.md is the only upstream source and ignores internal packages/* changelogs, preventing cross-package noise.
• Incremental diffing: It compares version blocks between the source and the docs files, copying only entries that are missing—no full-file rewrites, no duplicate lines.
• Automated translation: The English increment is translated to Chinese for docs/zh/release-notes/changelog.md using the agent’s language model, with the option to pause for human review before committing.
• Branch + PR discipline: The skill creates a dedicated branch (e.g., chore/sync-changelog-v1.4.2), commits the two file updates, and opens a PR with a clear title and description—ready for maintainer approval.
• Idempotent and safe: If run twice, it detects that the changelog is already synced and exits without side effects, avoiding duplicate PRs.

Practical scenarios

After a patch release with a hotfix

You shipped v1.4.2 with a critical bug fix. The changelog entry is short but must appear in both languages. The agent detects the missing version block, translates it, creates the branch, and opens a PR within minutes—before you even finish your coffee.

When multiple packages release at once

Your repo uses changesets and three packages bumped versions. Only the CLI package’s changelog matters for the docs site. The agent filters correctly and updates only the two intended files, avoiding the temptation to sync unrelated package notes.

During a busy release week with multiple versions

You’ve released v1.4.1 and v1.4.2 in the same week. The skill processes each increment sequentially, ensuring the docs changelog reflects both versions in chronological order, with proper translation for each.

Add it to your agent workflow

Install the skill using the OpenAgentSkill CLI:

npx skills add wangyuahn/nori-code --skill sync-changelog

Then invoke it after a successful npm publish. For example, in an agent prompt:

Run the sync-changelog skill now. The latest version is v1.4.2 and the source changelog is at apps/nori-code/CHANGELOG.md.

The agent will locate the skill definition, follow its steps, and produce a PR for your review.

Compare before adopting

Before adding this skill to your permanent toolchain, evaluate it against your release process: check the skill’s quality signals—does the README clearly state its scope and edge cases? Look at maintenance freshness: is the repo actively updated with the latest changesets version? Consider alternatives like writing your own script or using a generic file-sync agent; this skill wins if you need translation and PR automation out of the box. Finally, verify it fits your workflow—does your docs structure match the expected paths and do you want the optional human review step?

Why it is worth tracking

With 13 stars and a focused purpose, sync-changelog is a small but well-defined skill that demonstrates a real pain point in multi-package releases. Its quality signals are solid: explicit source-of-truth documentation, incremental logic, and a clean PR flow. Track it if you’re building agent workflows around release automation or if you maintain a docs site that mirrors a CLI changelog. Re-evaluate it when you adopt a new versioning tool or change your docs layout—the skill’s hardcoded paths may need adjustment. For a deeper look at its implementation and community updates, see the skill page on OpenAgentSkill.