メニュー
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill repo-syncコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | repo-sync |
| description | Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes) |
| type | reference |
| version | 1.1.0 |
| category | workspace-hub |
| last_updated | "2026-02-14T00:00:00.000Z" |
| source | internal |
| invoke | /repo-sync |
| capabilities | [] |
| requires | [] |
| see_also | [] |
| tags | ["git","sync","multi-repo","automation"] |
| related_skills | ["repo-structure","ecosystem-terminology"] |
| freedom | low |
Smart pull-all with automatic diagnosis and repair for the workspace-hub multi-repo ecosystem.
/repo-sync — Pull all repos, diagnose failures, and fix them.
Optional arguments:
/repo-sync pull — Pull all repos (default)/repo-sync status — Status check only, no pulls/repo-sync push — Push all repos with unpushed commitsrepository_sync pull <repo-name> — Pull one configured repository (for example ./scripts/repository_sync pull mkt-a)CLI syntax pitfall: repository_sync <repo-name> is not valid and returns Unknown command. If the user gives a bare repo name with repository_sync, infer the intended default operation as a single-repo pull and run ./scripts/repository_sync pull <repo-name> after a quick status check.
Run ./scripts/repository_sync pull all to attempt pulling every repo.
For each repo that failed, check:
Apply the appropriate fix per failure type:
| Failure | Fix |
|---|---|
| Detached HEAD (submodule) | git checkout main && git pull --no-rebase |
| Diverged branches | git pull --no-rebase (merge strategy) |
| Uncommitted changes blocking pull | git stash && git pull --no-rebase && git stash pop |
| Line-ending-only dirty tree | Diagnose with git diff --ignore-space-at-eol --shortstat; if empty, report as line-ending churn and do not normalize/discard without explicit user approval. See references/line-ending-only-dirty-working-tree.md |
| No upstream |
| Report only, no auto-fix |
| Deterministic generated-file conflict | Regenerate from the documented generator, validate with a parser, then stage; do not hand-merge arbitrary conflict hunks. See references/generated-file-conflict-regeneration.md |
| Large repo partial checkout / timed-out pull | Use no-untracked status probes, kill hung sync/status processes if needed, preserve recovery artifacts under .git/recovery-backups/, restore accidental tracked deletions; see references/large-repo-partial-checkout-recovery.md |
| Archived/read-only remote | Do not force workaround; preserve/export local-only commits and open a follow-up issue |
If a repo is ahead locally but push fails because the remote is archived or read-only:
git log @{u}..HEAD)git format-patch -1 <commit> --stdout > <workspace-hub-artifact>.patcharchive-only.This came up with pyproject-starter, where the remote was archived/read-only and the only ahead commit was a massive destructive sync commit. The safe action was to preserve the patch in repo artifacts and require explicit human review before any migration.
After pulling, run the encoding check against all work queue and skill files to surface any Windows-created UTF-16 / CRLF files that came in via the pull:
.claude/hooks/check-encoding.sh
This runs in warn-only mode (post-merge behaviour) — it reports bad files but does not block. Any files flagged should be converted and committed immediately:
# Convert a UTF-16 file to UTF-8
iconv -f UTF-16 -t UTF-8 <file> | sed 's/\r//' > /tmp/fixed.md
mv /tmp/fixed.md <file>
git add <file> && git commit -m "fix(encoding): convert <file> to UTF-8"
After the encoding check, spawn an ecosystem health agent in the background:
Task(
subagent_type="Bash",
description="Ecosystem health check",
prompt="Run the 14-check suite from /ecosystem-health skill. Report pass/fail/warn for each group.",
run_in_background=True
)
This does not block the pull summary. Report health results alongside repo status.
See /ecosystem-health skill for the full check suite and pass conditions.
When this skill is invoked, execute these steps:
For all repos:
./scripts/repository_sync pull all
For a single configured repo:
./scripts/repository_sync status <repo-name>
./scripts/repository_sync pull <repo-name>
Capture output. Identify repos marked with ✗ Failed or any nonzero command exit.
cd <repo_path>
# Check if on a branch
git branch --show-current # empty = detached HEAD
# Check for uncommitted changes
git status --porcelain
# Check divergence (only if on a branch with upstream)
git rev-list --count @{u}.. 2>/dev/null # ahead
git rev-list --count ..@{u} 2>/dev/null # behind
Run all independent repo fixes in parallel using the Bash tool.
Detached HEAD:
cd <repo_path> && git checkout main && git pull --no-rebase
Diverged branches:
cd <repo_path> && git pull --no-rebase
Uncommitted changes blocking pull:
cd <repo_path> && git stash && git pull --no-rebase && git stash pop
If stash pop has conflicts, report to user — do NOT auto-resolve.
Format as markdown table:
| Repo | Issue | Fix Applied | Result |
|------|-------|-------------|--------|
When an issue number is part of the sync/commit request, include a clickable GitHub issue hyperlink in the final report. Resolve it live with gh issue view <number> --json url --jq .url so the link is grounded in the current repository, not memory.
reset --hard without explicit user approvalgit status will show them as modified (new submodule pointer) — this is expectedstash pop fails with conflicts, stop and report to user--no-rebase on all pulls to avoid rebase surprises on diverged reposgenerate-index.py and other parsers silently. Fix immediately on detection.git add -A, commits on the repo's current branch, and pushes that branch before attempting broader branch-merging work.main or master) detected from GitHub / origin/HEAD; do not assume main.origin/<default> if available) so merges are isolated from the user's current working tree and local dirty state..claude/state/*, logs, generated reports). After a commit or failed push, always re-run git status and re-fetch before retrying; apparent ref-lock push failures may be stale-expectation races rather than true divergence.main while only a narrow generated report should be committed. If the report files are ignored, use git add -f for only those artifacts; if local main is behind or unrelated dirty state makes merge risky, create a clean temporary worktree from origin/main, cherry-pick the narrow report commit, push HEAD:main, verify the remote artifact, then remove the temporary worktree. See references/cron-report-push-from-dirty-main.md.logs/orchestrator/hermes/skill-patches.jsonl). Treat that as intentional repo-ecosystem metadata: inspect it, commit it separately, and only then declare the worktree clean.HEAD with origin/<branch>. Some workspace-hub hooks or concurrent syncs can leave the remote-tracking ref already equal to HEAD; if HEAD == origin/<branch> and ahead/behind is 0/0, report "push not needed" instead of pushing blindly.HEAD to a topic branch, open a PR against the protected branch, and report the PR URL plus the still-ahead local main state as a known exception until the PR merges.config/ai_agents/ai-tools-status.yaml can be regenerated with bash scripts/maintenance/ai-tools-status.sh and YAML-parsed before staging. See references/generated-file-conflict-regeneration.md.git diff --ignore-space-at-eol --shortstat. If that output is empty while normal git diff --shortstat is large, do not stash/pop, normalize, or discard automatically; report it as a non-blocking local working-tree condition and ask before changing line endings. See references/line-ending-only-dirty-working-tree.md.git push --no-verify may be necessary after verifying local/remote state.git status --porcelain -uall, full du, or full checkout/pull loops as the first recovery move. Start with no-untracked status and ahead/behind probes, then follow references/large-repo-partial-checkout-recovery.md..claude.partial-pull-backup-*, .codex.partial-pull-backup-*, or generated provider cache trees, preserve them inside .git/recovery-backups/ instead of committing or deleting them; they are recovery artifacts unless the user explicitly says otherwise.No destructive git operation (force-push, reset --hard, auto-resolve conflicts) shall be performed without explicit user confirmation — ever.
| Excuse | Reality |
|---|---|
| "The conflict is trivial — I can auto-resolve it" | Trivial-looking conflicts have destroyed production data. Stash pop conflicts go to the user, always. |
| "Force-push is safe here because nobody else uses this branch" | You do not have full visibility into all machines and sessions using this repo. Assume others are active. |
| "I need to reset --hard to get to a clean state" | Use git stash to preserve work, then pull. Hard reset is data destruction, not cleanup. |
| "The encoding check is slow, I'll skip it this time" | UTF-16 files crash parsers silently. Skipping the check means shipping a time bomb. |
These phrases signal you are about to violate the Iron Law:
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.