Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Git Cleanup

ASecurity

Cleans up stale git branches, merged branches, orphaned remote refs, and identifies large files in history. Use for periodic repository maintenance.

7 stars
0 votes
0 copies
1 views
Added 5/28/2026
ai-agentsbashgit

Security Analysis

A100/100

Scanned 5/28/2026

$npx -y skills add viknesh20-20/claude-code-tool-kit --skill git-cleanup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Cleanup?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Git Cleanup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/viknesh20-20-git-cleanup/badge)](https://www.skillsdirectory.com/skills/viknesh20-20-git-cleanup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: git-cleanup
description: "Cleans up stale git branches, merged branches, orphaned remote refs, and identifies large files in history. Use for periodic repository maintenance."
allowed-tools: Bash(git *)
---

# Git Repository Cleanup

## Current State
!`git branch -a 2>/dev/null | head -30`
!`git remote -v 2>/dev/null`
!`git stash list 2>/dev/null`

---

## Cleanup Steps

### Step 1: Identify Merged Branches
List local branches already merged into main/master:
```bash
git branch --merged main 2>/dev/null || git branch --merged master 2>/dev/null
```

**Present the list to the user and ask for confirmation before deleting.**

Safe to delete (already merged):
```bash
git branch -d <branch-name>
```

### Step 2: Identify Stale Remote Branches
Prune remote tracking refs that no longer exist:
```bash
git remote prune origin --dry-run
```

After confirmation:
```bash
git remote prune origin
```

### Step 3: Identify Old Unmerged Branches
List branches with no commits in the last 90 days:
```bash
git for-each-ref --sort=committerdate --format='%(committerdate:short) %(refname:short)' refs/heads/ | head -20
```

**Never delete unmerged branches without explicit user approval.**

### Step 4: Clean Up Stashes
List all stashes:
```bash
git stash list
```

For old stashes (>30 days), suggest review and cleanup.

### Step 5: Repository Size Analysis
Check for large files:
```bash
git rev-list --objects --all | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' | sort -k3 -n -r | head -20
```

### Step 6: Garbage Collection
```bash
git gc --auto
```

---

## Output

### Cleanup Summary
| Action | Count | Status |
|--------|-------|--------|
| Merged branches deleted | X | Done/Pending |
| Stale remote refs pruned | X | Done/Pending |
| Old stashes reviewed | X | Done/Pending |

### Branches NOT Deleted (unmerged)
List branches that were skipped with last commit date.

### Space Recovered
Before and after repository size (if gc was run).

---

## Rules
- **NEVER force-delete** (`git branch -D`) without explicit user confirmation
- **NEVER delete** main, master, develop, or release branches
- Always show what will be deleted before doing it
- Prefer `--dry-run` first, then execute

Attribution

viknesh20-20viknesh20-20
View sourceSee grades on GitHubMore from viknesh20-20 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →