Skylv Git Pruner

v1.0.0

Safely removes merged and stale Git branches. Identifies branches already on main/master. Triggers: clean branches, remove old branches, delete merged branch...

0· 120·0 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sky-lv/skylv-git-pruner.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Skylv Git Pruner" (sky-lv/skylv-git-pruner) from ClawHub.
Skill page: https://clawhub.ai/sky-lv/skylv-git-pruner
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install skylv-git-pruner

ClawHub CLI

Package manager switcher

npx clawhub@latest install skylv-git-pruner
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the instructions: all actions are Git operations (listing branches, categorizing by commit date/upstream, and deleting). The skill does not request unrelated credentials, binaries, or install extra tooling.
Instruction Scope
The SKILL.md stays on-topic (Git branch discovery and deletion) and includes safety steps (show list, exclude protected branches, require confirmation). However, several steps are vague (no exact commands to detect unpushed commits or to compute '90+ days' vs '30 days'), and one example uses 'findstr' (Windows-only), which may mislead agents on non‑Windows platforms. Vagueness could lead to unintended deletions if an agent exercises broad discretion.
Install Mechanism
No install spec or code files; instruction-only skills are lower risk because nothing is written to disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are requested — proportional to the stated purpose.
Persistence & Privilege
always is false and there is no request for persistent or elevated privileges; the skill does not attempt to modify other skills or system-wide settings.
Assessment
This skill appears to be what it says — a set of instructions for pruning Git branches — but follow these precautions before using it: - Run a dry run first: list candidate branches without deleting them (e.g., git branch --merged origin/main and inspect dates). Do not run deletion commands until you verify the list. - The SKILL.md omits exact commands for detecting unpushed commits and calculating commit age. Prefer well-known checks such as git log origin/branch..branch or git cherry -v origin/branch to detect unpushed commits, and use git log --since/--before or for-each-ref with committerdate for date-based filtering. - Be careful with platform-specific commands: the file uses findstr (Windows). On macOS/Linux replace with grep. Confirm the agent's execution environment before running any shell commands. - Avoid git branch -D unless you have confirmed there are no important unpushed commits. Prefer git branch -d and only force-delete when you understand the consequences. - Backup or test in a non-critical repository first. If the agent can execute commands autonomously, ensure it always asks explicit confirmation before performing deletions. If the skill were improved, request explicit, cross-platform commands for each detection step, and a safer deletion workflow (dry-run mode, explicit command examples for detecting unpushed commits, and clearer protected-branch patterns).

Like a lobster shell, security has layers — review code before you run it.

latestvk979c2g9wazhd7f83ww0g5zzn185739a
120downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Git Branch Pruner

Overview

Safely identifies and removes merged, stale, and orphaned Git branches.

When to Use

  • User asks to "clean up branches" or "delete merged branches"
  • Branch list is too long to manage

How It Works

Step 1: Identify main branch

git branch --show-current git remote show origin | findstr "HEAD branch"

Step 2: List all branches

git branch -a --format "%(refname:short) %(upstream:short) %(committerdate:short)"

Step 3: Categorize

Merged: already in main/master Stale: no commit in 90+ days Orphaned: no upstream tracking Active: recent commits under 30 days

Step 4: Safe deletion

  1. Always show user what will be deleted first
  2. Exclude protected branches: main, master, develop, release/*
  3. Exclude branches with unpushed commits
  4. Ask for confirmation before deletion

Output Format

Merged branches (safe to delete): feature-old-login -> DELETE bugfix-typo-2024 -> DELETE

Protected (do not delete): main <- current develop

Commands: git branch -d (safe) or git branch -D (force) Remote: git push origin --delete branch-name

Comments

Loading comments...