commit-suggest

Generate Conventional Commits messages from current git changes.

4|3|Updated May 2, 2026
One-click install
npx skills add https://github.com/ggemba/squad-mcp --skill commit-suggest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-suggest
Source: https://github.com/ggemba/squad-mcp/tree/main/skills/commit-suggest
Command: npx skills add https://github.com/ggemba/squad-mcp --skill commit-suggest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the effort and guesswork of writing a correct, Conventional Commits-style message by producing a ready-to-paste suggestion from your current git changes.

Core Features & Use Cases

  • Conventional Commits message generation: Produces an accurate subject (and an optional body when the “why” isn’t obvious) derived from staged changes when available.
  • Risk-aware, read-only safety: Uses an allowlist of git commands in read-only mode and never edits files, never runs commit/push actions, and never adds AI authorship trailers.
  • Security-minded output handling: Treats diff and log content as untrusted data, avoids leaking secrets, and warns if suspicious or credential-like content is present.
  • Use case: Before committing, quickly turn a feature, fix, docs update, or test change into a consistent message that matches the repo’s existing commit style.

Quick Start

Ask for a Conventional Commit suggestion for your current changes by using /commit-suggest (or “suggest a commit” / “commit message”) and then paste the output into your commit command.

Frequently Asked Questions about commit-suggest

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

FAQPage Schema
How do I generate a conventional commit message from git staged changes?

You can generate a conventional commit message by analyzing your git staged changes to produce a ready-to-paste text suggestion, including an optional body explaining the why.

Can I create a commit message suggestion if I only have unstaged changes?

Yes, commit message generation applies to staged-first preparation but also handles cases where only unstaged changes exist or both staged and unstaged changes are present.

Does generating git commit messages automatically run git commit or push actions?

No, the generation process uses an allowlist of read-only git commands, never edits files, and never runs commit or push actions to ensure safe workflow automation.

How are secrets and credentials handled during git diff summarization?

During diff summarization, diff and log content is treated as untrusted data to avoid leaking secrets, and warnings are provided if suspicious or credential-like content is detected.

Does the generated conventional commit message include AI attribution trailers?

No, the generated conventional commit output is plain text suitable for direct use in a git commit and explicitly omits any AI attribution trailers.