From b7e43910fb1a2173e857c4c6b7fa6af9f9ca1be7 Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Fri, 13 Mar 2026 15:33:25 -0700 Subject: [PATCH] fix(skills): require specific branch names based on what was refreshed --- .../compound-engineering/skills/ce-compound-refresh/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md b/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md index 759685b..276aef4 100644 --- a/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md +++ b/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md @@ -485,7 +485,7 @@ Use sensible defaults — no user to ask: | Context | Default action | |---------|---------------| -| On main/master | Create a descriptively named branch, commit, attempt to open a PR. If PR creation fails, report the branch name. | +| On main/master | Create a branch named for what was refreshed (e.g., `docs/refresh-auth-and-ci-learnings`), commit, attempt to open a PR. If PR creation fails, report the branch name. | | On a feature branch | Commit as a separate commit on the current branch | | Git operations fail | Include the recommended git commands in the report and continue | @@ -497,7 +497,7 @@ First, run `git branch --show-current` to determine the current branch. Then pre **If the current branch is main, master, or the repo's default branch:** -1. Create a branch, commit, and open a PR (recommended) +1. Create a branch, commit, and open a PR (recommended) — the branch name should be specific to what was refreshed, not generic (e.g., `docs/refresh-auth-learnings` not `docs/compound-refresh`) 2. Commit directly to `{current branch name}` 3. Don't commit — I'll handle it