clean-gone-branches
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
npx skills add fcakyon/claude-codex-settings --skill clean-gone-branches --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Clean Gone Branches Remove local git branches that have been deleted from the remote. ## Process 1. **Update remote references** - Run `git fetch --prune`. 2. **Inspect local state** - Run `git branch -vv` to find branches marked as `[gone]`. - Run `git worktree list` to see whether any of those branches still have worktrees. 3. **Remove worktrees first** - For each `[gone]` branch that still has a worktree, remove the worktree before deleting the branch. 4. **Delete the gone branches** - Delete each local branch marked as `[gone]`. 5. **Report the result** - List removed worktrees and deleted branches. - If there are no `[gone]` branches, report that nothing needed cleanup.
- Process
What does the clean-gone-branches skill do?
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
How do I install it?
Run `npx skills add fcakyon/claude-codex-settings --skill clean-gone-branches --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.