john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(ce-work): suggest branch rename when worktree name is meaningless (#451)

Browse Source 
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Trevin Chow
2026-03-30 00:49:19 -07:00
committed by GitHub
parent 42fa8c3e08
commit e872e15efa
2 changed files with 22 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
plugins/compound-engineering/skills/ce-work-beta/SKILL.md
View File

@@ -74,8 +74,17 @@ Determine how to proceed based on what was provided in `<input_document>`.
```
**If already on a feature branch** (not the default branch):
- Ask: "Continue working on `[current_branch]`, or create a new branch?"
- If continuing, proceed to step 3
First, check whether the branch name is **meaningful** — a name like `feat/crowd-sniff` or `fix/email-validation` tells future readers what the work is about. Auto-generated worktree names (e.g., `worktree-jolly-beaming-raven`) or other opaque names do not.
If the branch name is meaningless or auto-generated, suggest renaming it before continuing:
```bash
git branch -m <meaningful-name>
```
Derive the new name from the plan title or work description (e.g., `feat/crowd-sniff`). Present the rename as a recommended option alongside continuing as-is.
Then ask: "Continue working on `[current_branch]`, or create a new branch?"
- If continuing (with or without rename), proceed to step 3
- If creating new, follow Option A or B below
**If on the default branch**, choose how to proceed:

13
plugins/compound-engineering/skills/ce-work/SKILL.md
View File

@@ -73,8 +73,17 @@ Determine how to proceed based on what was provided in `<input_document>`.
```
**If already on a feature branch** (not the default branch):
- Ask: "Continue working on `[current_branch]`, or create a new branch?"
- If continuing, proceed to step 3
First, check whether the branch name is **meaningful** — a name like `feat/crowd-sniff` or `fix/email-validation` tells future readers what the work is about. Auto-generated worktree names (e.g., `worktree-jolly-beaming-raven`) or other opaque names do not.
If the branch name is meaningless or auto-generated, suggest renaming it before continuing:
```bash
git branch -m <meaningful-name>
```
Derive the new name from the plan title or work description (e.g., `feat/crowd-sniff`). Present the rename as a recommended option alongside continuing as-is.
Then ask: "Continue working on `[current_branch]`, or create a new branch?"
- If continuing (with or without rename), proceed to step 3
- If creating new, follow Option A or B below
**If on the default branch**, choose how to proceed: