commit-message-generating

Generate conventional commit messages from diffs for Shopware marketplace changes.

41|5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill commit-message-generating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message-generating
Source: https://github.com/shopwareLabs/ai-coding-tools/tree/main/.claude/skills/commit-message-generating
Command: npx skills add https://github.com/shopwareLabs/ai-coding-tools --skill commit-message-generating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates conventional commit messages for the Shopware AI Coding Tools marketplace repository by analyzing diffs to determine type, infer scope from plugin structure, and detect breaking changes, ensuring consistent and informative commit history.

Core Features & Use Cases

  • Infers commit type (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert) from diffs
  • Infers scope from paths under plugins/ to assign a meaningful plugin or infrastructure scope
  • Detects breaking changes and supports rewriting messages for existing commits
  • Works with staged, squash, and rewrite workflows to generate ready-to-use commit messages

Quick Start

Stage your changes and run the skill to generate a conventional commit message.

Frequently Asked Questions about commit-message-generating

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

FAQPage Schema
How do I generate conventional commit messages from git diffs automatically?

To generate conventional commit messages, you stage your git changes and run the skill to analyze diffs, infer the commit type and scope from plugin paths, and output a structured message with breaking-change notes.

How does inferring commit scope work for plugin marketplace changes?

Inferring commit scope works by analyzing file paths under the plugins/ directory in your diffs, assigning a meaningful plugin or infrastructure scope to the generated conventional commit message automatically.

Can I rewrite existing commit messages to follow conventional commit standards?

Yes, you can rewrite existing commit messages; the skill supports rewrite workflows alongside staged and squash workflows to detect breaking changes and produce standardized conventional commit messages.

What commit types are supported when generating messages from code changes?

Supported commit types include feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert, determined automatically by analyzing your staged git diffs.

Does this work with squash workflows for GitHub CI integration?

Yes, it works with squash workflows for GitHub CI integration by generating ready-to-use conventional commit messages complete with type, scope, subject, body, and breaking-change notes.