worktree-sparsity-eval

Use sparse checkout when working with large Git repositories to reduce disk space and improve checkout times. It prevents checking out the entire repository, which is beneficial for massive codebases like the Linux kernel or large monorepos.

Evaluate sparse checkout needs by collecting Git repository metrics including file count, total working tree size, and change locality. Comparing these against predefined thresholds recommends whether to enable sparse checkout.

Yes, sparse checkout works with Git worktrees in large monorepos to optimize repository management. It limits the files checked out to the working tree, reducing disk space usage and improving checkout performance.

Automate Git worktree creation by running the evaluation to collect repository metrics. The skill provides specific Git worktree creation commands with and without sparse checkout based on the evaluation results.

Sparse checkout in Git worktrees may not be beneficial if repository metrics like change locality and file count fall below predefined thresholds. It adds configuration overhead without yielding significant disk space or checkout time improvements for smaller repositories.