Github Sync Helper

Objectives

Codify GitHub/Git "basic operations" and common collaboration workflows into:

1. A clear command quick reference (explanation + when to use)
2. Executable one-click scripts (to avoid repetitive manual steps)
3. Common outputs that are "numbered" whenever possible, so the user can reply with a number to choose an item directly, such as from a repository list

Security and Constraints (Must Be Followed)

How to Run

• Script entry point: sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh <command> [options]

The script runs in the "current Git repository directory" and must be run inside a repository.

Quick Reference for Basic Git/GitHub Operations (Explanation + Corresponding Script)

Note: The script is intended to "turn common basic operations into reusable commands." For complex rebases or conflicts, using an interactive terminal is still recommended.

GitHub Platform Operations (API)

Unified requirement: env GITHUB_TOKEN is required.

Script Command List (gh_sync.sh)

Typical Workflows (Examples)

1) Push directly to main: empty directory -> restore directory -> push (the workflow you just used)

sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh empty-dir --dir self-improving-agent
sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh restore-dir --src /var/minis/skills/self-improving-agent --dst self-improving-agent
sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh commit --message "restore(self-improving-agent): sync from local"
sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh push-main

4) Replace only the contents of a target file in the repository (preserve the original path and filename), then commit and push

Applicable scenarios: The user asks to "replace only the content," "replace only the worker inside," or "preserve the original repository filename/path." The intent is: only overwrite the target file contents, without adding the source filename to the repository and without changing the target path in the repository.

Recommended execution order:

# 1. Pull/refresh the repository
repo_dir=/var/minis/workspace/<repo>
if [ -d "$repo_dir/.git" ]; then
  cd "$repo_dir" && git fetch --all --prune && git reset --hard origin/main
else
  gh repo clone <owner/repo> "$repo_dir"
fi

# 2. Content-only overwrite: overwrite the target file in the repository with the source file contents
cp <source_file> "$repo_dir/<target_path>"

# 3. If the Git identity is not configured, prefer reusing the GitHub display name and GitHub noreply email
cd "$repo_dir"
git config user.name '<GitHubDisplay Name>'
git config user.email '<login>@users.noreply.github.com'

# 4. Commit and push directly to main (only when the user explicitly requests commit/push)
git add <target_path>
git commit -m 'replace <target_path> content'
git push origin main

Key points:

• When the user says "replace content only," always interpret it as: preserve the original file path and filename in the repository, and overwrite only the content.
• Do not put the source filename directly into the repository; the target should still be the original file in the repository, such as worker.js.
• If the target path is known, overwrite that path directly; if it is unknown, first locate the target file in the repository and then replace it.
• If Author identity unknown is reported before committing, you can write the following in the current repository:
  • git config user.name '<GitHubDisplay Name>'
  • git config user.email '<login>@users.noreply.github.com'
• By default, run git fetch + git reset --hard origin/main first to avoid accidentally committing on an old working tree.
• If the user has already explicitly requested "commit" or "push," proceed directly without asking for confirmation again.

5) Delete all branches except main (local + remote)

sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh delete-branches --keep main

6) Do not create a branch; open a PR directly from fork:main to upstream:main

sh /var/minis/skills/github-sync-helper/scripts/gh_sync.sh pr \
  --upstream OpenMinis/MinisSkills \
  --head mowenyun:main \
  --base main \
  --title "sync: ..." \
  --body "..."

• Repository list output must use a Markdown table and include a Number column so the user can reply with a number to choose directly.
• Suggested fields: Number | Repository(owner/repo) | Visibility | Fork | Default branch | Last updated | URL
• Interaction suggestion: After the table, prompt: "Reply with the number to continue (clone/pull/commit and push/content-only replacement, etc.)."

Note: If the user needs more fields (description, language, stars), add --json ... to extend the output.