git-commit

Generate a squash-commit message summarizing branch changes since main.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sunbluesome/dotfiles --skill git-commit-sunbluesome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/sunbluesome/dotfiles/tree/main/.claude/ds/skills/git-commit
Command: npx skills add https://github.com/sunbluesome/dotfiles --skill git-commit-sunbluesome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a single, cohesive commit message that summarizes all changes on the current branch, specifically for squash and merge operations, reducing manual drafting effort.

Core Features & Use Cases

  • Generates a concise squash commit message from the branch history.
  • Analyzes commits since branching from main and produces a readable summary suitable for PRs.
  • Supports typical squash-and-merge workflows and consistent messaging across teams.

Quick Start

Ask this skill to generate a squash commit message for the current branch.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a squash commit message from branch history?▼

To generate a squash commit message from branch history, this Skill analyzes all commits since branching from main and aggregates them into a concise narrative. It produces a consistent, conventional-commit-style title and body suitable for PRs.

What is the best way to summarize commits for a squash and merge?▼

The best way to summarize commits for a squash and merge is to analyze the branch history, detect the main purpose of the changes, and generate a single cohesive commit message. This reduces manual drafting effort and ensures consistent messaging across teams.

Does this squash commit message generator require any specific dependencies?▼

No, this squash commit message generator does not require any specific external dependencies or components. You only need to ask it to generate a message for your current branch, and it will examine the branch history to produce the output.

Can I use this to format a pull request description from multiple commits?▼

Yes, you can use this to format a pull request description from multiple commits. It analyzes the commits since branching from main and produces a readable summary formatted as a conventional-commit-style title and body suitable for PRs.

When do I need to generate a conventional commit message for my branch?▼

You need to generate a conventional commit message for your branch when preparing for a squash and merge operation. This ensures that all individual changes on the branch are aggregated into a single, cohesive narrative with a consistent format.