Skip to content
TrustedSkillsbeta
Back to all skills

git-branch-cleanup

Checked
gotalab·v1.0.0·backend·MIT

|

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $

What we know about this skill

Publisher

gotalab

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned gotalab/skillport at 51334ae949.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
51334ae949
Manifest
.skills/experimental/git-branch-cleanup/SKILL.md
Scanned
1 file, 231 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the process of identifying and deleting stale or merged Git branches. It can filter branches based on whether they have been merged into a specified target branch, and delete those that match the criteria. The skill also allows for dry-run mode to preview changes before actual deletion occurs.

When to use it

  • Clean up after feature development: Regularly remove branches that have already been merged into main or develop.
  • Automate repository maintenance: Schedule periodic runs to keep the branch list manageable, especially in teams with frequent branching and merging.
  • Identify orphaned branches: Find branches that haven't been merged and may be candidates for deletion after investigation.
  • Prepare a repository for archiving: Before archiving a Git repository, remove unnecessary branches to reduce its size.

Key capabilities

  • Filters branches based on merge status with a target branch.
  • Supports dry-run mode for previewing deletions.
  • Allows specification of the target branch for merge comparison.
  • Provides clear output indicating which branches will be deleted (or would be, in dry-run mode).

Example prompts

  • "Clean up all merged branches into main."
  • "Dry run: Show me what branches would be deleted if I cleaned up branches merged into develop."
  • "Delete branches that have been merged into release/1.0 and are older than 6 months."

Tips & gotchas

The skill requires access to a Git repository with appropriate permissions to delete branches. Always run in dry-run mode first to verify the intended branches will be affected before executing the actual deletion.