clean
The /clean command removes merged or stale Git branches from both local and remote repositories while preserving main, dev, and gh-pages branches. Use this command to declutter your repository after merging pull requests and to maintain a clean branch list, with safeguards requiring user confirmation before deleting remote branches and preventing force-deletion of unmerged branches without explicit approval.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.claude/commands/git/clean.md -o ~/.claude/commands/clean.mdclean.md
Clean up stale branches that have been merged or are no longer needed. ## Steps 1. **List local branches** to delete (excluding `main`, `dev`, `gh-pages`): ```bash git branch | grep -v -E '^\*|main$|dev$|gh-pages$' ``` Report what will be deleted. If no branches found, say "No local branches to clean" and skip to step 3. 2. **Delete local branches** that are fully merged: ```bash git branch -d <branch-name> ``` If a branch is not fully merged, report it to the user and ask whether to force-delete. Do NOT force-delete without confirmation. 3. **List remote branches** to delete (excluding `main`, `dev`, `gh-pages`, `HEAD`): ```bash git branch -r | grep -v -E 'origin/main$|origin/dev$|origin/gh-pages$|origin/HEAD' ``` Report what will be deleted. If no branches found, say "No remote branches to clean" and skip to step 5. 4. **Confirm with the user** before deleting remote branches. Show the full list and wait for approval. Then delete: ```bash git push origin --delete <branch-names> ``` 5. **Prune stale remote refs**: ```bash git remote prune origin ``` 6. **Report final state**: ```bash git branch # local git branch -r # remote ``` Present a summary: | Item | Count | |------|-------| | Local branches deleted | N | | Remote branches deleted | N | | Remaining local | main, dev | | Remaining remote | origin/main, origin/dev, origin/gh-pages |
Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>
Stage working tree changes and create a Conventional Commit (no push).
Stage, commit, and push the current branch following git governance rules.
Create a pull request from the current branch.
Run the full 8-phase plugin audit pipeline on a skill directory.
Run the local review gate before pushing.
Run the security scan gate before pushing.
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.