github-devops-repository-cleanup

Remove stale Git branches older than 30 days and temporary files.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill github-devops-repository-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-devops-repository-cleanup
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/devops/github-devops-repository-cleanup
Command: npx skills add https://github.com/GDSDN/kord-aios --skill github-devops-repository-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps maintain a clean and organized Git repository by identifying and removing outdated branches and unnecessary temporary files, saving developers time and reducing clutter.

Core Features & Use Cases

  • Stale Branch Identification: Detects merged branches older than 30 days.
  • Temporary File Removal: Cleans up common temporary files like .DS_Store, Thumbs.db, and .log files.
  • Safety Checks: Includes safeguards against deleting critical branches like main or master.
  • Use Case: Regularly run this Skill on your project to automatically prune old feature branches and clear out build artifacts, ensuring your repository stays lean and manageable.

Quick Start

Run the github-devops-repository-cleanup skill to clean up the current repository.

Frequently Asked Questions about github-devops-repository-cleanup

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

FAQPage Schema
How do I clean up stale Git branches older than 30 days in my repository?

To clean up stale Git branches older than 30 days, you can run this Skill to automatically identify and remove outdated merged branches while preserving critical ones like main or master.

What is the best way to remove temporary files like .DS_Store and .log from a Git repository?

Removing temporary files like .DS_Store and .log from a Git repository is handled by identifying and clearing these common artifacts to reduce clutter and keep the project lean.

Do I need Git CLI and GitHub CLI to prune old feature branches remotely?

Yes, you need both Git CLI and GitHub CLI installed to perform remote operations for pruning old feature branches, with built-in safety checks ensuring critical branches are not deleted.

Can I plan repository maintenance before actually deleting outdated branches?

Yes, you can use the pre-flight planning mode to review repository maintenance actions before executing them, alongside autonomous and interactive modes for cleaning outdated branches.

What safety checks exist to prevent accidental deletion of critical Git branches?

Safety checks are built into the repository cleanup process to explicitly prevent the accidental deletion of critical Git branches such as main and master during stale branch removal.