manage-assets

Diagnose repository bloat by listing oversized tracked files and historical blobs.

50|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/subinium/vibesubin --skill manage-assets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-assets
Source: https://github.com/subinium/vibesubin/tree/main/plugins/vibesubin/skills/manage-assets
Command: npx skills add https://github.com/subinium/vibesubin --skill manage-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repos accumulate binary bloat and oversized assets that slow clones, CI, and onboarding. This skill surfaces bloats without editing code or rewriting history, enabling teams to see where large files or asset directories accumulate.

Core Features & Use Cases

  • Diagnoses oversized tracked files and historical blobs that inflate repository size.
  • Detects growing asset directories and potential ignore gaps to reduce future bloat.
  • Hands off remediation to the appropriate specialized skills (refactor-verify, manage-secrets-env, fight-repo-rot) rather than performing destructive changes itself.

Quick Start

Provide a read-only bloated-assets report for the current repository and prepare hand-off steps for remediation.

Frequently Asked Questions about manage-assets

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

FAQPage Schema
How do I find large files bloating my git repository history?

Finding large files bloating your git repository involves diagnosing oversized tracked files and historical blobs. This read-only analysis surfaces size-based findings and growing asset directories without modifying code or rewriting history.

What is the best way to analyze repo bloat before deciding on an LFS migration?

Analyzing repo bloat before an LFS migration requires quantifying oversized binary artifacts and historical blobs. This diagnostic approach identifies growing asset directories and ignore gaps, handing off remediation actions rather than performing destructive changes itself.

Can I detect growing asset directories in a large repo without modifying the codebase?

You can detect growing asset directories in a large repo without modifying the codebase by running a read-only diagnostic. It identifies potential ignore gaps and asset growth patterns, preparing hand-off steps for remediation while keeping your history intact.

Does checking repository bloat require rewriting git history to remove large blobs?

Checking repository bloat does not require rewriting git history to remove large blobs. The diagnostic process is strictly read-only, surfacing duplicates and oversized files so you can hand off appropriate actions to specialized skills for safe remediation.

Why does my large repository have slow clones and how do I quantify the binary bloat?

Large repositories have slow clones because of accumulated binary bloat and oversized assets. You quantify the binary bloat by diagnosing oversized tracked files and historical blobs, which surfaces size-based findings to address clone and CI slowdowns.