lucking7/compound-engineering-skills · Archived
Clean up local branches whose remote tracking branch is gone.
npx skills add lucking7/compound-engineering-skills --skill ce-clean-gone-branches
This repository is archived — consider an actively maintained alternative.
Execute work efficiently while maintaining quality and finishing features
5 installsCreate structured plans for multi-step tasks -- software features, research workflows, events, …
5 installsExplore requirements and approaches through collaborative dialogue, then write a right-sized re…
4 installsStructured code review using tiered persona agents, confidence-gated findings, and a merge/dedu…
4 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
>- Choose and create the right Neon branch type for testing and development. Use when users ask…
5.9K installsClean up local branches whose remote tracking branch is gone. Use when the user says "clean up …
1.8K installsCheck out two branches in separate worktrees, start both dev servers on different ports, screen…
1 installsClean up local branches whose remote tracking branch is gone. Use when the user says "clean up …
236 installsOther skills from lucking7/compound-engineering-skills · top by installs.
npx skills add lucking7/compound-engineering-skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Alternate registries and mirrors of this skill.
npx skills add https://github.com/everyinc/compound-engineering-plugin
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,462 B
SUMMARY.md
345 B
Delete local branches whose remote tracking branch has been deleted, including any associated worktrees.
Run the discovery script to fetch the latest remote state and identify gone branches:
bash scripts/clean-gone[scripts/clean-gone](./scripts/clean-gone)
The script runs git fetch --prune first, then parses git branch -vv for branches marked : gone].
If the script outputs NONE, report that no stale branches were found and stop.
Show the user the list of branches that will be deleted. Format as a simple list:
These local branches have been deleted from the remote:
- feature/old-thing
- bugfix/resolved-issue
- experiment/abandoned
Delete all of them? (y/n)Wait for the user's answer using the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), requestuserinput in Codex, askuser in Gemini, askuser in Pi (requires the pi-ask-user extension). Fall back to presenting the list in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.
This is a yes-or-no decision on the entire list -- do not offer multi-selection or per-branch choices.
If the user confirms, delete each branch. For each branch:
git worktree list | grep "\\[$branch\\]")git worktree remove --force "$worktree_path"git branch -D "$branch"Report results as you go:
Removed worktree: .worktrees/feature/old-thing
Deleted branch: feature/old-thing
Deleted branch: bugfix/resolved-issue
Deleted branch: experiment/abandoned
Cleaned up 3 branches.If the user declines, acknowledge and stop without deleting anything.