From 6f93b20cd1f787455d3e153171597fe0b8022f0f Mon Sep 17 00:00:00 2001 From: gavrielc Date: Fri, 3 Apr 2026 11:25:57 +0300 Subject: [PATCH] fix: relax breaking change detection to match [BREAKING] anywhere in line Previously required `[BREAKING]` at the start of the line, missing entries formatted as `- [BREAKING] ...` in changelogs. Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/skills/update-nanoclaw/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/skills/update-nanoclaw/SKILL.md b/.claude/skills/update-nanoclaw/SKILL.md index 496d409..9de18e6 100644 --- a/.claude/skills/update-nanoclaw/SKILL.md +++ b/.claude/skills/update-nanoclaw/SKILL.md @@ -188,7 +188,7 @@ After validation succeeds, check if the update introduced any breaking changes. Determine which CHANGELOG entries are new by diffing against the backup tag: - `git diff ..HEAD -- CHANGELOG.md` -Parse the diff output for lines starting with `+[BREAKING]`. Each such line is one breaking change entry. The format is: +Parse the diff output for added lines (starting with `+`) that contain `[BREAKING]` anywhere in the line. Each such line is one breaking change entry. The format is: ``` [BREAKING] . Run `/` to . ```