squash-merge

To squash merge a GitHub pull request with a conventional commit message, the skill uses the gh CLI to merge the PR while automatically generating a comprehensive commit message that summarizes all branch changes according to repository conventions.

Yes, you can automatically generate a commit message that adheres to project conventions when merging a PR, as the skill detects specific commit styles like Conventional Commits and crafts the subject and body content based on the PR details and commit history.

The best way to summarize branch changes into a single commit when finalizing a feature branch is using a squash merge, which combines all commits into one meaningful commit with a concise subject line and a detailed body explaining the changes.

Yes, you need the gh CLI installed and configured to squash merge pull requests from the command line, because the skill relies on this dependency to interact with GitHub, identify commit conventions, and finalize the merge.

Your squash merge commit message may not match repository conventions if the commit history or PR details are unclear, but this skill specifically identifies your project's commit conventions and generates subject and body content designed to follow them.

You need to use a squash merge instead of a standard merge when you want to finalize a feature branch by combining all incremental commits into a single, meaningful commit that clearly explains the changes and their purpose without cluttering the main history.