AI Agent Hub
Back to skills
Git Manager icon

Git Manager

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_992964b6/git-manager.

About this skill

What Problem It Solves

Managing multiple Git repositories often means scattered platforms, slow manual cloning or updates, and fragmented migration or Gitea operations. Git Manager bundles cross-platform batch operations into a few Python scripts: batch_clone.py, batch_pull.py, git_ops.py, and git_lfs.py, useful for engineers who need local workflows across GitHub, GitLab, Gitea, Bitbucket, and Azure.

How It Works

Core capabilities include:
- Batch cloning: specify an organization, user, or project with --platform, --type, and --id, control concurrency with --workers, and preview with --dry-run.
- Batch updates: batch_pull.py updates a local repository directory, with support for concurrency, rebase, and stash workflows.
- Single-repository operations: git_ops.py covers day-to-day and debugging commands such as merge, rebase, worktree, bisect, reflog, and grep.
- LFS and Gitea: git_lfs.py manages tracking rules; batch_clone.py can run migration, create an organization, and trigger mirror sync.

The typical workflow starts from a platform ID, selects the target platform and scope, then validates results with JSON output or a dry run. Keep tokens in environment variables, remember GitHub unauthenticated rate limits, avoid rebasing public branches, and confirm GitLab numeric group IDs and Gitea mirror settings in advance.

Use Cases

  • Clone all repositories under a GitHub org into a local directory, using concurrent workers to speed up the job.
  • Pull all repos from a GitLab group, preview with dry-run, then clone them for local inspection.
  • Migrate GitHub repos into Gitea, create the target organization, trigger mirror sync, and verify the sync state.
  • Use worktree to inspect multiple branches in parallel, or use bisect to find the problematic regression commit.

Best For

  • Platform engineers maintaining internal codebases who need to batch-sync GitHub or GitLab repositories.
  • DevOps engineers handling Gitea migration who need to import external repositories and configure organization mirror sync.
  • Software engineers managing large-file projects who need to track assets such as *.psd through Git LFS.
  • Backend engineers debugging regressions who need worktree and bisect to isolate problematic commits.