cleanup

Migrate to the default branch and delete obsolete Git branches with a status report.

54|3|Updated Feb 4, 2026

Search Tags:#git #cleanup #repository #status #hygiene #branch

Ready to run

npx skills add https://github.com/arcasilesgroup/ai-engineering --skill cleanup-arcasilesgroup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.agents/skills/cleanup
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill cleanup-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of cleaning up your Git repository by safely migrating to the default branch, aggressively deleting obsolete branches, and providing a comprehensive report on repository health.

Core Features & Use Cases

Safe Default Branch Migration: Ensures you are on the latest default branch (main or master) before cleanup.
Aggressive Branch Cleanup: Deletes merged, squash-merged, and stale remote-tracking branches.
Branch Status Reporting: Provides a detailed report of which branches were kept, deleted, and why.
Use Case: After completing several features and merging them, run this skill to clear out old feature branches and get a clear overview of your repository's current state.

Quick Start

Run the cleanup skill to perform a full repository hygiene operation.

Frequently Asked Questions about cleanup

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

FAQPage Schema

How do I clean up stale remote-tracking branches and merged local branches in Git?▼

To clean up stale remote-tracking branches, this skill safely migrates to the default branch, aggressively deletes obsolete branches, and generates a detailed per-branch status report. It handles merged, squash-merged, and stale remote-tracking branches.

What is the best way to automate Git repository hygiene after merging features?▼

Automating Git repository hygiene involves safely migrating to the default branch and aggressively deleting obsolete branches. This skill performs full repository hygiene, clearing old feature branches and providing a comprehensive report on repository health.

Does this branch cleanup skill handle squash-merged branches safely?▼

Yes, this branch cleanup skill safely handles squash-merged branches. It performs aggressive cleanup by deleting merged, squash-merged, and stale remote-tracking branches while ensuring you remain on the latest default branch.

Do I need Git installed on my PATH to perform repository branch cleanup?▼

Yes, you need Git installed and available on your PATH to perform repository branch cleanup. The skill requires Git to safely migrate to the default branch and aggressively delete obsolete branches.

How does this Git cleanup process report on repository health and branch status?▼

The Git cleanup process reports on repository health by generating a detailed per-branch status report. It provides a comprehensive overview of which branches were kept, deleted, and why, ensuring clear repository status visibility.

Why should I migrate to the default branch before deleting obsolete Git branches?▼

Migrating to the default branch before deleting obsolete Git branches ensures safe repository hygiene. This skill guarantees you are on the latest default branch (main or master) before aggressively cleaning up stale remote-tracking and merged branches.