commit-message-writing

Parse code diffs to generate conventional commit messages for Shopware core.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes code changes to produce consistent, conventional commit messages for Shopware core, streamlining collaboration and changelog quality.

Core Features & Use Cases

  • Detects squash-merge titles or branch commit messages and routes accordingly.
  • Analyzes diffs and infers scope from Shopware directory structure to generate precise type and scope.
  • Detects breaking changes and surfaces them in the footer when required.

Quick Start

Generate a conventional commit message from the current working branch changes.

Frequently Asked Questions about commit-message-writing

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

FAQPage Schema
How do I generate conventional commit messages from git diffs for Shopware core?

Generate conventional commit messages for Shopware core by parsing code diffs to infer the correct type and scope from the directory structure. The tool analyzes working branch changes and outputs a compliant subject with an optional body based on Shopware writing rules.

How does conventional commit scope detection work for Shopware directory structures?

Conventional commit scope detection for Shopware works by analyzing the code diff and inferring the scope directly from the affected directory structure. This ensures the generated commit message accurately reflects the specific module or area modified in the core codebase.

Can I use this to format squash-merge titles and feature-branch commit messages?

Yes, you can format both trunk squash-merge titles and feature-branch commit messages. The tool detects the merge type and routes the diff analysis accordingly to produce a conventional commit subject and body that aligns with Shopware writing rules.

How do I add breaking change footers to conventional commits in Shopware?

Add breaking change footers to conventional commits by letting the tool detect breaking changes within the code diff. It automatically surfaces these breaking changes in the commit message footer when required, ensuring changelog compliance for Shopware core updates.

What is the best way to automate Shopware commit message writing for pull requests?

Automate Shopware commit message writing by analyzing diffs from the current working branch to generate compliant conventional commit messages. It applies Shopware-specific writing rules to output a proper type, scope, and optional body, streamlining collaboration and changelog quality.

Does this conventional commit generator work without additional git dependencies?

Yes, the conventional commit generator works without additional dependencies. It directly parses the provided code diffs to infer scope and detect breaking changes, outputting the final compliant commit message subject and optional body independently.