commit-message-writing

Commit Message Generation

Generate conventional commit messages for Shopware core. Squash merge titles (title-only) for trunk merges and full commit messages (title + body) for branch work.

Output scope: Presents formatted commit message text. Does not create commits, write files, or modify git state.

Phase 1 — Detect Mode and Gather Context

Determine what we're generating — a squash merge title or a branch commit message.

1. Parse user input:
   • Commit ref provided (SHA, HEAD, HEAD~3, etc.) -> branch mode, resolve to SHA
   • Branch ref, "squash", "current branch", or "merge commit" -> squash mode
   • Nothing specific -> branch mode, use HEAD
2. Gather the diff:
   • Branch mode: git show <sha> --name-status --format='' and git show <sha> --format=''
   • Squash mode: Continue to step 3
3. Squash mode only — detect base branch: Load references/branch-and-pr-detection.md and execute Steps 1-4. Route as commit-message-writing.
4. Squash mode only — get branch diff:
   • git diff <base>...HEAD --stat and git diff <base>...HEAD
   • git log <base>..HEAD --oneline

Phase 2 — Analyze and Generate

Type Detection

Analyze the diff to determine the commit type. Priority-ordered decision tree:

1. Revert commit? -> revert
2. Only docs (*.md, docblocks, inline comments)? -> docs
3. Only formatting/whitespace changes? -> style
4. Only test files? -> test
5. Only build/dependency files (composer.json, package.json, Dockerfile)? -> build
6. Only CI config (.github/workflows/, .gitlab-ci.yml)? -> ci
7. Adds new user-facing functionality? -> feat
8. Fixes broken behavior? -> fix
9. Performance improvement (caching, query optimization, reduced allocations)? -> perf
10. Code restructuring without behavior change? -> refactor
11. Otherwise -> chore

When ambiguous (e.g., both feat and fix equally present), ask the user:

AskUserQuestion(
  question="This branch contains both new functionality and bug fixes. Which type best represents the primary purpose?",
  options=[
    {label: "feat", description: "The main goal is new functionality"},
    {label: "fix", description: "The main goal is correcting broken behavior"}
  ]
)