Diagnose pathological Git repository size before migration, CI, or contributor onboarding
Uses git-sizer to identify the specific size and history characteristics that make a repository painful to clone, fetch, repack, or work in. Use it when an agent needs evidence about large blobs, oversized trees, too many refs, or other Git pathologies before proposing cleanup.
What it does
Diagnose pathological Git repository size before migration, CI, or contributor onboarding
Uses git-sizer to identify the specific size and history characteristics that make a repository painful to clone, fetch, repack, or work in. Use it when an agent needs evidence about large blobs, oversized trees, too many refs, or other Git pathologies before proposing cleanup.
Prerequisites
Git 2.6 or newer and a full non-shallow clone of the repository being analyzed
Installation
Basic usage or getting-started notes:
-
git-sizer computes various size metrics for a local Git repository, flagging those that might cause you problems or inconvenience. For example:
-
Consider using "git notes" rather than tags to attach auxiliary information to commits (for example, CI build results).
-
Does the repository include too many objects? The more objects, the longer it takes for Git to traverse the repository's history, for example when garbage-collecting. Suggestions:
-
Extracted from upstream docs: https://raw.githubusercontent.com/github/git-sizer/HEAD/README.md
Documentation
Source
Capabilities
Install
Quality
deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 8 github stars · SKILL.md body (1,380 chars)