Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

commit-message-writing

/commit-message-writing

Pisze komunikaty commitów i tytuły squash merge dla repozytorium Shopware, analizując diffy i wnioskując zakres, w trybie pełnym lub samego tytułu.

Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pisze komunikaty commitów i tytuły squash merge dla repozytorium Shopware, analizując diffy i wnioskując zakres, w trybie pełnym lub samego tytułu.

Oryginalny opis (EN)

Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles (title-only) for trunk merges — the skill auto-detects which based on the current branch and PR target. Analyzes diffs, infers scope from Shopware's directory structure, and detects breaking changes. Do NOT activate during implementation work or when the user is still writing code; only when

Jak działa

  1. Phase 1 — Detect Mode and Gather Context
  2. Phase 2 — Analyze and Generate
  3. Phase 3 — Validate and Present
Sekcje z nagłówków SKILL.md, w oryginale · 124 linii, 675 słów
Podgląd SKILL.md
---
name: commit-message-writing
version: 1.6.6
model: sonnet
description: Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles (title-only) for trunk merges — the skill auto-detects which based on the current branch and PR target. Analyzes diffs, infers scope from Shopware's directory structure, and detects breaking changes. Do NOT activate during implementation work or when the user is still writing code; only when they are ready to capture a finished change. For commit messages in the ai-coding-tools marketplace repo itself, use the commit-message-generating skill instead.
allowed-tools: Read, Grep, Glob, Bash, AskUserQuestion
---

# 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"}
  ]
)
```

### Scope Detection

Delegate to references/scope-inference.md. Pass the list of changed file paths and the base branch (for commit history lookup in squash mode) or `HEAD~20` (for branch mode).

### Breaking Change Detection

Scan the diff for breaking changes:
- API signature changes (required parameters added, removed, or reordered)
- Public methods or classes removed or renamed
- Return types changed on public methods
- Database schema breaking changes (column removal, type change)
- Default behavior changed in ways that affect existing callers

If detected, add the `!` marker after scope in the output.

### Subject

Craft the subject line. Apply references/writing-rules.md.

- Imperative mood, lowercase, no period, max 72 characters total
- Informed by the diff (truth) and commit messages (intent context, squash mode only)
- Specific: name the component and behavior, not abstract descriptions
- No PR number (GitHub adds it during squash merge)
- No AI/tool attribution

### Body (Branch Mode Only)

Craft the body. Apply references/writing-rules.md.

- WHY-not-WHAT: explain motivation, root cause, trade-offs
- Blank line between subject and body
- Single continuous lines per paragraph (no hard-wrapping)
- Concrete: class names, config keys, method signatures
- If breaking: include `BREAKING CHANGE:` footer with brief description

## Phase 3 — Validate and Present

Before presenting, validate the generated message against references/writing-rules.md:

1. **Em dash check:** Literally search the generated text for `—` and `–`. Replace any found.
2. **Banned vocabulary:** Scan for words from the banned list. Replace with plain alternatives.
3. **Subject rules:** Verify imperative mood, lowercase, no period, within 72 characters, no attribution.
4. **Body rules (branch mode):** Verify WHY-not-WHAT, no diff restatement, concrete specifics.

**Squash mode:**
```
type(scope): subject
```

**Branch mode:**
```
type(scope): subject

Body explaining why this change was made.
```

Or with breaking change:
```
type(scope)!: subject

Body explaining why this change was made.

BREAKING CHANGE: brief description of what breaks.
```

After the message, show brief reasoning (one line each):
- **Type:** `feat` — adds new maxLength parameter to attribute entity fields
- **Scope:** `dal` — all changes within DataAbstractionLayer, matches trunk history

Done. No file writes, no git operations beyond read-only commands.
Pliki w paczce (5)
  • .agent-skills 1 KB
  • SKILL.md 5 KB
  • references/branch-and-pr-detection.md 2 KB
  • references/scope-inference.md 4 KB
  • references/writing-rules.md 11 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · shopwarelabs/ai-coding-tools100MIT
seyhunak/skilldeck100MIT

Migawka bazy z 13.11.2026 · wersja paczki 860d40e08084 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100pr-description-writing
    Pisze i poprawia opisy pull requestów kierowanych do gałęzi trunk w repozytorium shopware/shopware.
  • 100feature-branch-pr-writing
    Pisze opisy pull requestów w repozytorium rdzenia Shopware dla PR kierowanych do gałęzi funkcji innej niż trunk, wykrywając gałąź docelową.
  • 100pr-commit-message
    Pisze i poprawia komunikaty merge commit i squash commit dla pull requestów, zachowując powód zmiany na podstawie PR i powiązanych zgłoszeń.
  • 100squash-commit
    Pisze komunikat squash commit w formacie Conventional Commits dla pull requestu, na podstawie commitów i opisu.
  • 100writing-commit-messages
    Pisze lub sprawdza komunikat commita, squasha albo merge commita, gdy zmiana jest gotowa do zapisania, rozpoznając tryb z argumentów.
  • 100merge-commit
    Pisze komunikat merge lub squash-merge commita dla bieżącej gałęzi, gotowy do skopiowania do procesu scalania.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.