From 3d2ac239b2d5757dcbe186f9131a21091f2276bb Mon Sep 17 00:00:00 2001
From: Lawrence Chen <54008264+lawrencecchen@users.noreply.github.com>
Date: Sat, 21 Feb 2026 04:21:11 -0800
Subject: [PATCH] chore: update release skill metadata

---
 .gitkeep                | 0
 skills/release/SKILL.md | 3 +--
 2 files changed, 1 insertion(+), 2 deletions(-)
 create mode 100644 .gitkeep

diff --git a/.gitkeep b/.gitkeep
new file mode 100644
index 00000000..e69de29b
diff --git a/skills/release/SKILL.md b/skills/release/SKILL.md
index 19e8fa6d..0f5cd1ff 100644
--- a/skills/release/SKILL.md
+++ b/skills/release/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: release
-description: Prepare and ship a cmux release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release.
+description: "Prepare and ship a cmux release end-to-end: choose the next version, curate user-facing changelog entries, bump versions, open and monitor a release PR, merge, tag, and verify published artifacts. Use when asked to cut, prepare, publish, or tag a new release."
 ---
 
 # Release
@@ -63,4 +63,3 @@ Run this workflow to prepare and publish a cmux release.
 - Include only user-visible changes.
 - Exclude internal-only changes (CI, tests, docs-only edits, refactors without behavior changes).
 - Write concise user-facing bullets in present tense.
-