changeset-generator
/changeset-generator
Generuje pliki changeset na podstawie zmian, na prośbę użytkownika albo na końcu implementacji funkcji, gdy trzeba domknąć i sfinalizować zmiany.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Generuje pliki changeset na podstawie zmian, na prośbę użytkownika albo na końcu implementacji funkcji, gdy trzeba domknąć i sfinalizować zmiany.
Oryginalny opis (EN)
Generates changeset files based on changes. Use when user asks to create a changeset or at the end of a feature implementation, when the user asks to wrap up or finalize changes
Jak działa
- Step 1: Detect change source
- Step 2: Gather context
- File naming
- File format
- Validate before writing
- Good:
Podgląd SKILL.md
---
name: changeset-generator
description:
Generates changeset files based on changes. Use when user asks to create a changeset or at the end of a feature implementation, when the user asks to wrap up or finalize changes
disable-model-invocation: true
---
> AGENTS.md is the canonical source for shared LikeC4 repository instructions, including changeset policy. This file is a task-specific wrapper for generating changeset files.
Generate changeset files based on current branch changes or staged files. Use AGENTS.md for shared LikeC4 changeset policy, including when a changeset is needed, release type, package exclusions, and summary style.
# 1. Identify Changes
## Step 1: Detect change source
Determine where to read changes from, in this priority order:
```bash
# First: check for staged changes
STAGED=$(git diff --staged --name-only)
if [ -n "$STAGED" ]; then
echo "Using staged changes"
else
# Second: check for branch changes vs main
BRANCH_DIFF=$(git diff --name-only main...HEAD 2>/dev/null)
if [ -n "$BRANCH_DIFF" ]; then
echo "Using branch changes vs main"
else
# Third: check for uncommitted changes
UNCOMMITTED=$(git diff --name-only)
echo "Using uncommitted changes"
fi
fi
```
Use whichever source has changes. If none have changes, tell the user and stop.
## Step 2: Gather context
For **staged changes:**
```bash
git diff --staged --name-only # changed files
git diff --staged --stat # change size overview
git diff --staged -- '*.ts' '*.tsx' # actual code diff for key files
```
For **branch changes:**
```bash
git diff --name-only main...HEAD # changed files
git log --oneline main..HEAD # commit list
git log --format="%s%n%b" main..HEAD # commit messages for intent
```
Read the actual diff for non-trivial files when commit messages are vague — file names alone are often insufficient for writing a good summary.
**Conventional Commits triage hints:**
- `feat:` / `fix:` — usually needs a changeset
- `chore:` / `test:` / `refactor:` — usually skip unless user-facing
# 2. Map Files to Packages
Group changed files by their package:
- `packages/<name>/*` → read `packages/<name>/package.json` for the package name
- `apps/<name>/*` → read `apps/<name>/package.json`
- `styled-system/<name>/*` → read `styled-system/<name>/package.json`
Apply the changeset policy in AGENTS.md to decide whether each changed package has public impact. If no packages remain after filtering, tell the user there are no user-facing changes and stop.
# 3. Generate Summary
Follow the summary policy in AGENTS.md. Reference issues when relevant, for example `Fixes [#123](https://github.com/likec4/likec4/issues/123)`.
# 4. Create Changeset File
Use the release type required by AGENTS.md for every selected package.
## File naming
Derive the filename from the summary — lowercase, hyphens, descriptive:
- `add-cloud-shape.md`
- `fix-diagram-zoom-reset.md`
- `element-notes-feature.md`
## File format
Create at `.changeset/<name>.md`:
```markdown
---
'<package-name>': patch
'<another-package>': patch
---
<summary>
```
## Validate before writing
Before creating the file, verify each package name exists:
```bash
# For each package in your changeset, confirm it's real
cat packages/<name>/package.json | grep '"name"'
```
If a package name doesn't match, fix it before writing the changeset.
# 5. Confirm with User
Show the user the changeset content and file path before or after writing. If something looks off, iterate.
# Examples
## Good:
```markdown
---
'@likec4/diagram': patch
---
Add reset manual layout button with tooltip guidance
```
```markdown
---
'@likec4/core': patch
'@likec4/diagram': patch
---
First iteration of element notes feature:
- Add notes property to elements
- Display visual indicator on diagrams
```
# Notes
- Combine multiple packages in one changeset if they're part of the same feature
- If a branch has multiple independent features, suggest creating separate changesets for each
Wersje
W bazie nie ma innych skilli o nazwie changeset-generator.
Migawka bazy z 13.11.2026 · wersja paczki ebfeaf0509b7 (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
- 100changeset
Tworzy changeset dla zmian w gałęzi i pisze noty wydania dla zmienionych pakietów. - 100changeset
Generuje plik changeset opisujący zmiany bieżącego PR, z losową nazwą w .changeset, listą pakietów, typem podbicia wersji i podsumowaniem dla użytkownika do 80 znaków. - 96changeset
Pisze wpisy changeset do wydań, opisując zmiany w pakietach i ich wersjonowanie. - 100changeset
Tworzy changeset w monorepo Astro: dodaje plik changeset do PR, pisze wpis do changelogu i dokumentuje podbicie wersji pakietu. - 100changesets
Tworzy lub odświeża plik .changeset/<slug>.md dla bieżącej gałęzi albo stwierdza, że changeset nie jest wymagany, zwłaszcza przy zmianach w packages/**. - 100add-changeset
Pisze changeset dla agentic-seo-check jako plik, bez pytań interaktywnych, w stylu changelogu.