Why does it back-merge master to develop instead of release to develop?

Merging master to develop ensures that develop receives the exact merge commit from master, keeping branch histories aligned and preventing divergent commit SHAs that cause future merge conflicts.

What happens if the master PR isn't merged yet?

The skill verifies the PR state using the GitHub CLI and will stop if the PR is still open or closed without merging, instructing you to complete the merge on GitHub first.

Does this skill handle versioning formats?

Yes, it enforces a strict N.N.N format (e.g., 1.53.0) and will reject invalid formats to ensure your git tags remain consistent and clean.

Does it require specific tools to be installed?

This skill requires the Git CLI and the GitHub CLI (gh) to be authenticated and available in your environment to manage PRs and tags.

Git Flow Release Completion

Name: Git Flow Release Completion
Author: enterspeedhq

byenterspeedhq

0•

Deployment & DevOps

Automates the final steps of a Git Flow release by tagging master, back-merging to develop, and cleaning up release branches.

This skill streamlines the conclusion of a software release process following the Git Flow methodology. After a master pull request is merged, it handles the verification of the merge state, generates and pushes the appropriate version tag to the master branch, and automates the critical back-merge from master to develop. This ensures branch synchronization and prevents future merge conflicts while automatically cleaning up local release branches to maintain a clean workspace.

Key Features

01Version-specific tagging on the master branch with push verification

02Automated PR state verification via GitHub CLI

030 GitHub stars

04Master-to-develop back-merge PR creation for history synchronization

05Automated local release branch cleanup after successful completion

06Strict error handling and version format validation

Use Cases

01Standardizing the tagging and cleanup process across a development team

02Ensuring develop and master branches remain synchronized after a release cycle

03Finalizing a production release after the master branch PR is approved and merged

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add enterspeedhq/agent-skills gitflow-release-finish

For use in Claude.ai and ChatGPT

Key Features

01Version-specific tagging on the master branch with push verification

02Automated PR state verification via GitHub CLI

030 GitHub stars

04Master-to-develop back-merge PR creation for history synchronization

05Automated local release branch cleanup after successful completion

06Strict error handling and version format validation

Use Cases

01Standardizing the tagging and cleanup process across a development team

02Ensuring develop and master branches remain synchronized after a release cycle

03Finalizing a production release after the master branch PR is approved and merged

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add enterspeedhq/agent-skills gitflow-release-finish

For use in Claude.ai and ChatGPT