Changeset Generator

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:

# 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:

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:

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:

---
'<package-name>': patch
'<another-package>': patch
---

<summary>

Validate before writing

Before creating the file, verify each package name exists:

# 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:

---
'@likec4/diagram': patch
---

Add reset manual layout button with tooltip guidance

---
'@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