From e3e7748c564a24e74d86fdf847dd499284404cc8 Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Fri, 13 Mar 2026 15:16:03 -0700 Subject: [PATCH] fix(skills): remove prescriptive branch naming in compound-refresh Let the agent generate a reasonable branch name based on context and repo conventions instead of prescribing a date-based format that would collide on multiple runs per day. --- .../compound-engineering/skills/ce-compound-refresh/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md b/plugins/compound-engineering/skills/ce-compound-refresh/SKILL.md index 99e3d95..e2ec303 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 branch (`docs/compound-refresh-YYYY-MM-DD`), commit, attempt to open a PR. If PR creation fails, report the branch name. | +| On main/master | Create a descriptively named branch, 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 |