Token导航 LogoToken导航

Agent Skill · 运维和基础设施

repo-sync(仓库同步)

repo-sync 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

repo-sync 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 1,515。

总安装 523周安装 22GitHub Stars 8下载 183核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:repo-sync(仓库同步)
来源仓库:https://github.com/vamseeachanta/workspace-hub
仓库路径:skills/repo-sync
安装命令:
npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-sync
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-sync

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

repo-sync 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。它能帮助 Agent 同步项目状态、协调团队协作并确保工作一致性。

可通过 npx skills add 命令从指定 GitHub 仓库安装,具体用法请参考原始 README。安装前建议确认权限范围和维护状态,注意是否触发联网或文件读写操作。repo-sync 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/repo-sync

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-sync;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

repo-sync 怎么安装?

在终端执行 npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-sync。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

repo-sync 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

repo-sync 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

repo-sync 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

repo-sync 用的人多吗?

公开数据是累计安装 523 次,近一周安装 22 次,下载 183 次,GitHub 8 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

repo-sync 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
repo-sync

仓库同步 · 本页

5238需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Repository Sync Skill

Efficiently manage and synchronize 26+ Git repositories with bulk operations, status monitoring, and coordinated commits.

Quick Start

# Check status of all repositories
./scripts/repository_sync status all

# Pull latest from all repos
./scripts/repository_sync pull all

# Sync (commit + push) all work repos
./scripts/repository_sync sync work -m "End of day sync"

When to Use

  • Starting a work session and need to pull latest changes across all repos
  • End of day sync to commit and push all pending changes
  • Checking which repos have uncommitted changes or are behind remote
  • Coordinating branch changes across multiple related repositories
  • Releasing updates across the entire workspace ecosystem

Prerequisites

  • Git installed and configured with SSH keys
  • Access to all repositories in workspace-hub
  • ./scripts/repository_sync script available and executable
  • Repository URLs configured in config/repos.conf

Overview

This skill enables efficient management of multiple Git repositories in the workspace-hub ecosystem. It provides tools for bulk operations, status monitoring, and coordinated synchronization across all repositories.

Quick Reference

Common Commands

# List all repositories
./scripts/repository_sync list all

# Check status of all repos
./scripts/repository_sync status all

# Pull latest from all repos
./scripts/repository_sync pull all

# Commit and push all repos
./scripts/repository_sync sync all -m "Update message"

# Work with specific category
./scripts/repository_sync pull work
./scripts/repository_sync sync personal -m "Personal updates"

Repository Categories

Work Repositories

Business and client projects:

  • digitalmodel - Digital model platform
  • energy - Energy analysis tools
  • frontierdeepwater - Deepwater engineering
  • aceengineer-admin - Admin platform
  • aceengineer-website - Company website

Personal Repositories

Personal projects and experiments:

  • Side projects
  • Learning repositories
  • Personal tools

Viewing Categories

# List work repos
./scripts/repository_sync list work

# List personal repos
./scripts/repository_sync list personal

# List all repos
./scripts/repository_sync list all

Core Operations

1. Status Check

View the state of all repositories:

./scripts/repository_sync status all

Output indicators:

  • 🟢 Clean: No changes, up to date
  • 🔴 Uncommitted: Has local changes
  • 🟣 Unpushed: Has commits not pushed
  • 🔵 Behind: Remote has updates
  • 🟡 Not cloned: Repository missing locally

2. Pull Operations

Fetch and merge from remote:

# Pull all repositories
./scripts/repository_sync pull all

# Pull only work repos
./scripts/repository_sync pull work

# Pull specific repo
./scripts/repository_sync pull digitalmodel

3. Commit Operations

Stage and commit changes:

# Commit all with default message
./scripts/repository_sync commit all

# Commit with custom message
./scripts/repository_sync commit all -m "Update dependencies"

# Commit work repos only
./scripts/repository_sync commit work -m "Weekly sync"

4. Push Operations

Push committed changes to remote:

# Push all repositories
./scripts/repository_sync push all

# Push work repos
./scripts/repository_sync push work

5. Full Sync (Commit + Push)

Complete synchronization in one command:

# Sync all repos
./scripts/repository_sync sync all -m "End of day sync"

# Sync work repos
./scripts/repository_sync sync work -m "Client updates"

Branch Management

List Branches

# Show branches in all repos
./scripts/repository_sync branches all

# Show branches in work repos
./scripts/repository_sync branches work

Fetch Remote Branches

Track all remote branches locally:

./scripts/repository_sync fetch-branches all

Sync with Main

Update feature branches with main:

# Merge main into current branches
./scripts/repository_sync sync-main all

# Rebase instead of merge
./scripts/repository_sync sync-main all --rebase

Switch Branches

Switch all repos to a specific branch:

# Switch to main
./scripts/repository_sync switch all main

# Switch to feature branch
./scripts/repository_sync switch work feature/new-design

Configuration

Repository URLs

Configure in config/repos.conf:

# Repository URL Configuration
digitalmodel=git@github.com:username/digitalmodel.git
energy=git@github.com:username/energy.git
aceengineer-admin=git@github.com:username/aceengineer-admin.git

Categories

Defined in .gitignore:

digitalmodel/        # Work
energy/              # Work
personal-project/    # Personal
mixed-repo/          # Work, Personal

Configure Repositories

# Edit configuration
./scripts/repository_sync config

# Refresh repository list
./scripts/repository_sync refresh

Workflows

Daily Development Workflow

# Morning: Pull latest
./scripts/repository_sync pull all

# During day: Work on code...

# End of day: Sync everything
./scripts/repository_sync sync all -m "$(date +%Y-%m-%d) updates"

Feature Branch Workflow

# Start feature in all work repos
./scripts/repository_sync switch work feature/new-feature

# Develop across repos...

# Keep in sync with main
./scripts/repository_sync sync-main work

# Push feature branches
./scripts/repository_sync push work

# Return to main
./scripts/repository_sync switch work main

Release Workflow

# Create release branch
./scripts/repository_sync switch work release/v1.2.0

# Final sync and push
./scripts/repository_sync sync work -m "Release v1.2.0 preparation"

# After merge, back to main
./scripts/repository_sync switch work main
./scripts/repository_sync pull work

Batch Operations

Selective Operations

Target specific repositories:

# Multiple specific repos
./scripts/repository_sync sync digitalmodel energy -m "Update"

# Pattern-based (if supported)
./scripts/repository_sync sync "ace*" -m "Ace project updates"

Parallel Execution

For faster operations on many repos:

# Built-in parallelization
./scripts/repository_sync pull all --parallel

# Or using xargs
ls -d */ | xargs -P 4 -I {} git -C {} pull

Execution Checklist

  • Verify SSH authentication (ssh -T git@github.com)
  • Check repository configuration (./scripts/repository_sync list all)
  • Run status check before operations (./scripts/repository_sync status all)
  • Review changes in repos with uncommitted work
  • Execute bulk operation with appropriate scope (all/work/personal)
  • Verify operation success with status check
  • Resolve any conflicts or errors reported

Error Handling

Merge Conflicts

When conflicts occur:

# Status will show conflicts
./scripts/repository_sync status all

# Resolve manually in affected repo
cd affected-repo
git status
# Fix conflicts...
git add .
git commit -m "Resolve conflicts"

# Continue with other repos
./scripts/repository_sync sync all

Stale Branches

Clean up old branches:

# List stale remote-tracking branches
git remote prune origin --dry-run

# Prune stale branches
git remote prune origin

Recovery

If things go wrong:

# Reset to remote state
cd repo-name
git fetch origin
git reset --hard origin/main

# Or restore from backup
git reflog
git reset --hard HEAD@{2}

Authentication Issues

# Verify SSH key
ssh -T git@github.com

# Check credential helper
git config --global credential.helper

Network Issues

# Test connectivity
git ls-remote origin

# Use HTTPS fallback
git remote set-url origin https://github.com/user/repo.git

Permission Denied

# Check file permissions
ls -la .git/

# Fix permissions
chmod -R u+rwX .git/

Metrics & Success Criteria

  • Sync Time: All repos synced in < 5 minutes
  • Status Accuracy: 100% accurate status reporting
  • Error Rate: < 1% failed operations
  • Recovery Time: Conflicts resolved within 10 minutes
  • Coverage: All 26+ repos included in sync operations

Integration Points

With Workspace CLI

# Launch interactive menu
./scripts/workspace

# Navigate: Repository Management → Repository Sync Manager

With AI Agents

Agents can use repository sync for:

  • Coordinated code changes
  • Cross-repo refactoring
  • Synchronized releases
  • Documentation updates

Related Skills

Windows / Git Bash Workarounds

These are learned from 44+ sync sessions on Windows MINGW64:

Path Issues

  • Trailing spaces in remote filenames prevent checkout — use git config core.protectNTFS false or skip those files
  • Long paths: enable git config --global core.longpaths true
  • Symlinks require admin — use git config core.symlinks false as fallback

Line Endings

  • Shell scripts must use LF, not CRLF — verify with file script.sh
  • Fix: dos2unix script.sh or git config core.autocrlf input

MINGW Root Path

  • while ["$(pwd)"!= /] loops never terminate on MINGW (root is /d/, not /)
  • Use WORKSPACE_HUB env var for path resolution, not runtime pwd traversal
  • Project key derivation: pwd → /d/workspace-hub/digitalmodel → D--workspace-hub-digitalmodel

Stash Handling

  • Always stash uncommitted changes before pull: git stash push -m "pre-sync"
  • After pull, git stash pop — if conflicts occur, report to user, don't auto-resolve
  • Check stash list: git stash list to avoid orphaned stashes accumulating

Force-Pushed Refs

  • When submodule remote was force-pushed: git fetch origin && git reset --hard origin/main
  • Detect divergence: git rev-list --count HEAD..origin/main (behind) and ..HEAD (ahead)
  • Never rebase diverged branches — always merge or hard-reset after user confirmation

Unregistered Submodules

  • Check .gitmodules before assuming a directory is a submodule
  • git submodule status shows registered vs unregistered

.gitignore Conflicts

  • When remote adds files matching local.gitignore: git add -f <file> to force-track

Best Practices

Commit Messages

Use consistent format:

[scope] action: description

Examples:
[all] update: Dependency refresh
[work] fix: Security patches
[docs] add: API documentation

Frequency

  • Pull: Start of each work session
  • Commit: After completing logical units
  • Push: End of work session or before breaks
  • Sync: Daily minimum

Verification

Always verify before pushing:

# Check what will be pushed
./scripts/repository_sync status all

# Review specific repo changes
cd repo-name && git diff origin/main

References


Version History

  • 1.2.0 (2026-02-12): Added MINGW root path, stash handling, divergence detection from /insights analysis of 65+ sync sessions
  • 1.1.0 (2026-01-02): Upgraded to SKILL_TEMPLATE_v2 format - added Quick Start, When to Use, Execution Checklist, Error Handling consolidation, Metrics, Integration Points
  • 1.0.0 (2024-10-15): Initial release with bulk operations, branch management, workflows, error handling, workspace integration

平台分布

Claude Code

26.87%
按下载量换算49

OpenCode

23.69%
按下载量换算43

Codex

17.91%
按下载量换算33

windsurf

12.27%
按下载量换算22

trae

7.02%
按下载量换算13

Cursor

3.67%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills