clean-gone-branches
Clean Gone Branches removes local Git branches whose remote counterparts have been deleted. It first updates remote references and identifies branches marked as gone, then deletes any associated worktrees before removing the branches themselves. Use this skill when maintaining a repository and needing to eliminate stale local branches that no longer exist on the remote.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/clean-gone-branches && cp -r /tmp/clean-gone-branches/plugins/github-dev/skills/clean-gone-branches ~/.claude/skills/clean-gone-branchesSKILL.md
# 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.
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.