Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

merge-commit

/merge-commit

Pisze komunikat merge lub squash-merge commita dla bieżącej gałęzi, gotowy do skopiowania do procesu scalania.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
25.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
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.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 komunikat merge lub squash-merge commita dla bieżącej gałęzi, gotowy do skopiowania do procesu scalania.

Argumenty

/merge-commit [optional hint, e.g. 'version bump' or 'breaking change']
Oryginalny opis (EN)

Use when drafting a merge or squash-merge commit message for the current branch, to copy into the merge workflow.

Jak działa

  1. Procedure
  2. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 126 linii, 879 słów
Podgląd SKILL.md
---
name: merge-commit
description: "Use when drafting a merge or squash-merge commit message for the current branch, to copy into the merge workflow."
allowed-tools: ["Bash", "Read"]
argument-hint: "[optional hint, e.g. 'version bump' or 'breaking change']"
disable-model-invocation: true
---

# Generate Merge Commit Message

Draft a merge commit message for the current branch. It is the
user-facing, product-level summary that becomes the commit on the main
branch, whether the merge is a merge commit or a squash. Write it per
`../../references/prose-rules.md`.

User hint: $ARGUMENTS

## Procedure

### 1. Gather context

Follow `../../references/branch-context.md` to find the base and gather the branch's change.

### 2. Analyze changes

- Review the full diff and all commits, not only the latest.
- Classify the change: feature, fix, refactor, version bump, CI, docs,
  breaking change, runtime version drop.
- Note any PR number visible in the branch name or the user's hint.
- Describe the net shipped result: collapse fixups,
  reverts-then-re-adds, and WIP states. Leave out rename history,
  `### Fixes` for behavior that never shipped, and "no longer X" framing
  unless a user of the latest published release experienced the old
  name, behavior, or bug.

### 3. Read project conventions

Read `AGENTS.md` and `CLAUDE.md` for merge commit conventions. When the
project uses a scope format such as `scope(type[detail])`, match it in
the title.

### 4. Draft the message

#### Title line

- Under 70 characters, counting the ` (#N)` suffix.
- Ends with ` (#N)` when the PR number is known (a number in the hint,
  the branch name, or the branch's PR). The suffix belongs to the merge
  commit title only; commits on the branch never carry `#N`. When the
  number is unknown, leave the suffix off and tell the user to append it.
- Describes the impact, what changed for the user, not the
  implementation.

#### Body, proportional to the change

- Small change (1-3 file fix, simple bump): title only.
- Medium change (feature, targeted refactor, fix with a root cause):
  an opening paragraph of 2-4 sentences on what changed and why, then
  plain bullets for specific changes.
- Large change (multi-module feature, major refactor, migration): a
  structured body from the patterns below.

Bullets add detail the opening paragraph lacks; never restate it.

Add no `Co-Authored-By`, "Generated with", or other tool trailer, and no
emoji.

Wrap body lines at 72 characters. Never break a URL, hash, path, stack
trace, or long identifier mid-token; let that line run long.

#### Body patterns, use only what applies

- Features, refactors, bug fixes: opening paragraph (what and why),
  plain bullets, `Breaking changes:` with migration guidance,
  cross-references (`Fixes #N` only for an issue number the user, the branch name, or a commit supplied; `See also:`, companion PR links), and
  version compatibility notes.
- Bug fixes with a non-obvious root cause: a root-cause paragraph,
  numbered reproduction steps if they help, and the affected versions
  in a sentence when the bug is version-specific.
- API refactors with migration paths: old and new names as `old -> new` bullets for renamed
  methods, parameters, or modules; deprecation notices with a timeline.
- Version bumps: `v1.2.3 -> v1.3.0` notation, and per-file scope
  notes when files change different dependencies.
- Runtime version drops: the dropped version and why.
- Build and infra migrations: before/after tooling and why.
- Multi-module sync results: companion PR links, design decisions
  and trade-offs, and a qualitative test coverage summary.

Use only URLs, versions, and dates present in the diff, lockfile, or
fetched this run; omit the rest.

#### What not to include

- Test counts or passing numbers ("875 tests pass")
- Git SHAs, file-level line numbers, or the number of files changed
- Details the reviewer can see in the diff or `git log`

### 5. Present the message

Do not run any git write command; the user pastes the message into
their merge workflow (GitHub merge button, `git merge --edit`, the
squash-and-merge dialog).

Reply in this shape, as plain text outside any code fence, with plain bullets, no bold (never `- **Label:** ...`), and no local paths:

````text
Merge commit message for 3 commits on chore/bump-ruff:

```text
deps(chore[ruff]) Bump ruff to 0.9.2 (#58)

Picks up the fix for false positives in the import-sorting rule.

- Bump ruff from v0.8.6 -> v0.9.2 in the lint extra.
- Reformat two files the new release now flags.
```

The PR number came from the branch name, and the base is the local origin/main, which may be stale.
````

After the message, add one line only for a fact the user must act on: where the PR number came from, the number to append when none was found, or a base other than `origin/<trunk>`. Always name the base and say it is the local `origin/<trunk>`, which may be stale, unless the user fetched it this session. Do not explain the message's wording or the commit history.

A run that stops early (empty log, no base) is one sentence stating the stop and that nothing changed, then what the user must do. State the first stop reason only, one cause, and name one next step: do not list other possible causes or mention tools that were unavailable, and no speculation about other problems, no colon-delimited aside, no local paths. Reply in this shape:

```text
chore/bump-ruff has no commits ahead of origin/main, so no message was drafted and nothing changed. Commit your changes, then run this again.
```

## Rules

Never run `git merge`, `git commit`, or any write operation; output only.
Never force-push or run destructive git commands.
Pliki w paczce (2)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB

Wersje

W bazie nie ma innych skilli o nazwie merge-commit.

Migawka bazy z 13.11.2026 · wersja paczki f4a794438bf9 (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-merge-commit
    Przygotowuje komunikat merge lub squash-merge commita dla bieżącej gałęzi, gotowy do skopiowania w procesie scalania.
  • 95hk-merge-pr
    Scala pull request przez squash, pisząc wiadomość commita z jego commitów i stopki atrybucji repozytorium.
  • 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.
  • 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ń.
  • 100merge-strategy
    Opisuje strategie scalania git w sidecar: konflikty, merge kontra rebase, squash merge, szablony komunikatów commita, domyślne ustawienia i chronione gałęzie.

Uwagi i zgłoszenia

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