fcakyon/clean-gone-branches
plugins/github-dev/skills/clean-gone-branches/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add fcakyon/claude-codex-settings clean-gone-branchesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 3:49 AM36.1s1 file scanned
SKILL.md
- name:
- clean-gone-branches
- description:
- 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".
Clean Gone Branches
Remove local git branches that have been deleted from the remote.
Process
-
Update remote references
- Run
git fetch --prune.
- Run
-
Inspect local state
- Run
git branch -vvto find branches marked as[gone]. - Run
git worktree listto see whether any of those branches still have worktrees.
- Run
-
Remove worktrees first
- For each
[gone]branch that still has a worktree, remove the worktree before deleting the branch.
- For each
-
Delete the gone branches
- Delete each local branch marked as
[gone].
- Delete each local branch marked as
-
Report the result
- List removed worktrees and deleted branches.
- If there are no
[gone]branches, report that nothing needed cleanup.
Related Skills
fcakyon/setup
tools
VerifiedTrustedCommunity
This skill should be used when user asks to "set up overleaf", "configure overleaf cookie", "overleaf auth failed", "overleaf 401", "overleaf session expired", "overleaf unauthorized", or needs to install or refresh their Overleaf session cookie for the overleaf-skills plugin.
674SKILL.mdUpdated May 10, 2026
fcakyon/review-overleaf
documentation
VerifiedTrustedCommunity
This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tracked LaTeX repo.
658SKILL.mdUpdated May 3, 2026
fcakyon/dokploy-deploy
tools
VerifiedTrustedCommunity
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
654SKILL.mdUpdated Apr 26, 2026
fcakyon/stripe-best-practices
development
VerifiedTrustedCommunity
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
645SKILL.mdUpdated Apr 4, 2026