What problem does it solve?
Patch releases on release/patch/YYYYMMDD branches revert CHANGELOG.md and version files to the last stable release, so a naive merge into main produces many conflicts. This Skill encodes the exact resolution rules for each file type so the merge-back PR is correct.
Core Features & Use Cases
- Scoped change detection: Diffs only the last two commits of the release branch to identify touched
version_client.txt, CHANGELOG.md, and pom.xml files.
- Guided file reconciliation: Reference docs define how to merge
version_client.txt (take release-branch dependency-version, keep main's current-version) and CHANGELOG.md (insert the patch entry under the Unreleased section).
- Deterministic pom regeneration: Runs
eng/versioning/update_versions.py --skip-readme so pom.xml files are regenerated and READMEs stay untouched.
- Use Case: After the July 2026 patch release ships, ask the Skill to prepare the merge-back PR for
release/patch/20260701 into main, and it produces a correctly reconciled branch ready for review.
Quick Start
Prepare the merge-back PR for release/patch/20260701 into main.