skills.rest
gtapps
gtappsCOMMUNITY
Explore all skills by this author →
GitHub

dev-cleanup

Identify and clean up stale or merged Git branches with operator confirmation.

69|12|Updated Mar 23, 2026
Search Tags:#automation#git#safety#cleanup#branch-management#dev-workflows
One-click install
npx skills add https://github.com/gtapps/claude-code-hermit --skill dev-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-cleanup
Source: https://github.com/gtapps/claude-code-hermit/tree/main/plugins/claude-code-dev-hermit/skills/dev-cleanup
Command: npx skills add https://github.com/gtapps/claude-code-hermit --skill dev-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lists and offers to clean up stale or merged git branches in a local repo, reducing clutter and keeping the branch namespace healthy across sessions.

Core Features & Use Cases

  • Detects merged and stale branches based on protected branches and recent activity.
  • Cross-references session notes and pending tasks to avoid deleting branches tied to ongoing work.
  • Provides a safe, operator-confirmed cleanup flow with an audit log of deletions.

Quick Start

Run the dev-cleanup skill to scan for merged or stale branches and propose safe deletions with operator confirmation.

Frequently Asked Questions about dev-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up stale Git branches in a local repository?▼

You can clean up stale Git branches by scanning your local repository for merged or inactive branches, cross-referencing pending tasks, and proposing safe deletions that require operator confirmation before removal.

How does branch cleanup avoid deleting active work across multi-session workspaces?▼

Branch cleanup avoids deleting active work by cross-referencing session notes and pending tasks against recent branch activity and protected branches, ensuring ongoing development is skipped during the deletion process.

Can I automatically delete merged branches without manual confirmation?▼

No, merged branches cannot be deleted without manual confirmation because the cleanup flow enforces safety guardrails by requiring operator confirmation before deletion and logging all changes for auditability.

What is the best way to manage branch clutter in continuous dev workflows?▼

The best way to manage branch clutter in dev workflows is to automate the detection of stale and merged branches, enforcing auditability and operator confirmation to safely maintain a healthy branch namespace across sessions.

Does Git branch cleanup work with protected branches?▼

Yes, Git branch cleanup works with protected branches by explicitly detecting them and excluding them from deletion proposals, ensuring your core repository branches remain untouched during the stale branch cleanup process.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Branches

List and visualize Git branch status with remote tracking and synchronization.

Community
Intermediate
mixomatmixomat

clean-gone-branches

Delete local git branches marked [gone] while skipping worktree branches.

Community
Intermediate
evanharmon1evanharmon1
2

orient

Audit git repository state and manage GitHub issue task claims.

Community
Intermediate
dyoshikawadyoshikawa
1

clean-branches

Identify and delete stale local and remote-tracking git branches.

Community
Intermediate