Git仓库扫描器

Scan local directories to report Git repository status and metadata.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/Leochens/LifeOs --skill git-leochens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git仓库扫描器
Source: https://github.com/Leochens/LifeOs/tree/main/src/components/modules/git-scanner
Command: npx skills add https://github.com/Leochens/LifeOs --skill git-leochens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps discover and manage multiple local Git repositories by scanning a filesystem path and reporting branch, uncommitted changes, last commit, and remote URL so users can quickly identify repositories that need attention.

Core Features & Use Cases

  • Scans a specified directory tree with configurable traversal depth to find Git repositories.
  • Returns structured repository details including name, path, branch, has_uncommitted, last_commit, and remote_url, and supports filtering by all/clean/dirty status.
  • Use case: audit a developer workspace before a release to find repos with uncommitted changes or compile a list of active projects grouped by branch.

Quick Start

Use the Git repository scanner to scan /Users/username/projects at depth 5 and list repositories with uncommitted changes.

Frequently Asked Questions about Git仓库扫描器

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

FAQPage Schema
How do I find local Git repositories with uncommitted changes across multiple project folders?

To find local Git repositories with uncommitted changes, scan a specified directory tree to discover repositories and report their status, filtering results to show only those with dirty working directories.

Can I configure the traversal depth when scanning a developer workspace for Git repos?

Yes, you can configure the traversal depth when scanning a developer workspace for Git repos, allowing you to control how deep the filesystem search goes to locate repository folders.

What details are reported when auditing local Git repositories in a directory?

When auditing local Git repositories, the scan reports structured details including the repository name, path, current branch, uncommitted status, last commit, and remote URL.

How do I group local repositories by branch before a release audit?

Group local repositories by branch before a release audit by scanning the filesystem path and compiling a list of active projects based on the reported branch and status of each repository.

Does the Git repository scanner work without external dependencies?

Yes, the Git repository scanner works without external dependencies, requiring only a local filesystem path to scan and an optional depth configuration to begin discovering repositories.

What is the best way to list all Git repositories in a large local projects directory?

The best way to list all Git repositories in a large local projects directory is to run a filesystem scan with configurable depth to locate and return structured objects for every repository found.