From cd03d449cb9cfb48592cdfef9c77efa73fdb15bf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aleix=20Conchillo=20Flaqu=C3=A9?= Date: Fri, 6 Feb 2026 15:12:58 -0800 Subject: [PATCH] Update changelog skill with skip rules and allowed types --- .claude/skills/changelog/SKILL.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/.claude/skills/changelog/SKILL.md b/.claude/skills/changelog/SKILL.md index 0feb6b92c..89e13a40e 100644 --- a/.claude/skills/changelog/SKILL.md +++ b/.claude/skills/changelog/SKILL.md @@ -7,23 +7,30 @@ Create changelog files for the important commits in this PR. The PR number is pr ## Instructions -1. First, check what commits are on the current branch compared to main: +1. Skip changelog for: documentation-only, internal refactoring, test-only, CI changes. + +2. First, check what commits are on the current branch compared to main: ``` git log main..HEAD --oneline ``` -2. For each significant change, create a changelog file in the `changelog/` folder using the format: +3. For each significant change, create a changelog file in the `changelog/` folder using the format: + Allowed types: `added`, `changed`, `deprecated`, `removed`, `fixed`, `security`, `performance`, `other` - `{PR_NUMBER}.added.md` - for new features - - `{PR_NUMBER}.added.2.md`, `{PR_NUMBER}.added.3.md` - for additional new features + - `{PR_NUMBER}.added.2.md`, `{PR_NUMBER}.added.3.md` - for additional entries of the same type - `{PR_NUMBER}.changed.md` - for changes to existing functionality - `{PR_NUMBER}.fixed.md` - for bug fixes - `{PR_NUMBER}.deprecated.md` - for deprecations + - `{PR_NUMBER}.removed.md` - for removed features + - `{PR_NUMBER}.security.md` - for security fixes + - `{PR_NUMBER}.performance.md` - for performance improvements + - `{PR_NUMBER}.other.md` - for other changes -3. Each changelog file should at least contain a main single line starting with `- ` followed by a clear description of the change. +4. Each changelog file should at least contain a main single line starting with `- ` followed by a clear description of the change. -4. If the change is complicated, changelog files can have indented lines after the main line with additional details or code samples. +5. If the change is complicated, changelog files can have indented lines after the main line with additional details or code samples. -5. Use ⚠️ emoji prefix for breaking changes. +6. Use ⚠️ emoji prefix for breaking changes. ## Example