From d1a9c88b30a3c3866a6af1c3f534f2e6d95b89d7 Mon Sep 17 00:00:00 2001 From: Dan Connolly Date: Thu, 8 Oct 2026 18:35:03 -0500 Subject: [PATCH] fix: make skill frontmatter valid YAML A ": " inside a plain-scalar description is a parse error; use a folded block scalar instead. Co-Authored-By: Claude Opus 5.5 (1M context) --- silent-failures-are-evil/SKILL.md | 3 ++- yarn-lock-separate-commit/SKILL.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/silent-failures-are-evil/SKILL.md b/silent-failures-are-evil/SKILL.md index 5ce94ec..f0440e6 100644 --- a/silent-failures-are-evil/SKILL.md +++ b/silent-failures-are-evil/SKILL.md @@ -1,6 +1,7 @@ --- name: silent-failures-are-evil -description: No silent failures — use when writing or reviewing error handling: catch blocks, promise rejections, fallbacks for unsupported features, or any branch that treats a result as "didn't work"; when a UI shows a failure with nothing logged; when someone says "silent failure". Every failure path leaves a trace in the logs, and no failure is invented without checking what the API actually returns. +description: >- + No silent failures — use when writing or reviewing error handling: catch blocks, promise rejections, fallbacks for unsupported features, or any branch that treats a result as "didn't work"; when a UI shows a failure with nothing logged; when someone says "silent failure". Every failure path leaves a trace in the logs, and no failure is invented without checking what the API actually returns. --- # Silent failures are evil diff --git a/yarn-lock-separate-commit/SKILL.md b/yarn-lock-separate-commit/SKILL.md index c321ba3..6d1b547 100644 --- a/yarn-lock-separate-commit/SKILL.md +++ b/yarn-lock-separate-commit/SKILL.md @@ -1,6 +1,7 @@ --- name: yarn-lock-separate-commit -description: yarn.lock in its own commit — use when changing Yarn dependencies (package.json deps, workspace renames, yarn install), when organizing or reviewing commits that touch yarn.lock, when a rebase conflicts on yarn.lock, or during a retcon. Every lockfile change ships alone as `chore: Update yarn.lock`, after the package.json commit that caused it. +description: >- + yarn.lock in its own commit — use when changing Yarn dependencies (package.json deps, workspace renames, yarn install), when organizing or reviewing commits that touch yarn.lock, when a rebase conflicts on yarn.lock, or during a retcon. Every lockfile change ships alone as `chore: Update yarn.lock`, after the package.json commit that caused it. --- # yarn.lock in a separate commit