sync-dev-from-master

Automating dev branch synchronization after a release requires generating a standardized pull request from master to dev. This skill uses git and gh CLI to create the sync PR automatically, enforcing merge-commit-only policies to maintain repository history integrity.

Dev branches fall behind master when hotfixes are cherry-picked directly into production, causing version skew. To fix this, a synchronization pull request must be created from master to dev, resolving any merge conflicts that arise in versioning files during the process.

Preventing squash merges from breaking git branch history requires enforcing merge-commit-only policies during dev-master synchronization. This skill applies safety guardrails to the pull request workflow, ensuring the merge commit history remains intact and consistent across branches.

Yes, you need the gh CLI and git installed to automate dev-master pull request creation. These tools manage the local branch creation, remote repository interactions, and PR template population required to successfully execute the post-release synchronization workflow.

Version file conflicts during dev-master synchronization are handled through a structured conflict resolution workflow. When cherry-picked hotfixes cause version skew, the skill identifies conflicting versioning files and guides the merge conflict resolution process within the generated pull request.

Yes, you can use this workflow to generate a pre-filled pull request template for release management. It automates PR creation by populating standardized templates with correct metadata, providing a consistent structure for synchronizing your dev branch with the latest release version.