git:20260320.d5121e4 to git:20260801.3cb01ce

+ General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull, fetch, merge, rebase, tag, release, issues, actions, labels, milestone, protected branches, fork, PR, sync to upstream, delete branches, restore after emptying a directory, push directly to main, or one-click sync.

+ ## 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)

+ | No. | Rule | Reason |

+ | 1 | **Do not output tokens**: No command may echo or print `$GITHUB_TOKEN` to stdout | Prevent leaks |

+ | 2 | **Require a second confirmation for dangerous operations**: deleting branches, emptying directories, forced overwrites, force pushes, and direct pushes to main | These operations are hard to reverse |

+ | 3 | Use "branch + PR" collaboration by default; only "push directly to main" when the user explicitly requests it | Reduce the risk of damaging the main branch |

+ | 4 | Run `git status` before push/pull | Prevent accidental commits or overwrites |

+ ## 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)

+ | No. | Category | Operation | One-sentence explanation | Common command | Script support |

+ | 1 | Initialize | init | Turn the current directory into a Git repository | `git init` | `init` |

+ | 2 | Get code | clone | Download a repository from a remote to local | `git clone <url>` | `clone` |

+ | 3 | Remote | remote | Manage remotes such as origin/upstream | `git remote -v/add/set-url/remove` | `remotes/add-remote/add-upstream/set-remote-url/remove-remote` |

+ | 4 | Branch | branch | View, create, or delete branches | `git branch -a/-d/-D` | `branches/create-branch/delete-branches` |

+ | 5 | Switch | checkout/switch | Switch to a branch | `git switch <b>` | `checkout` |

+ | 6 | View changes | status/diff/log | View working tree changes, diffs, or history | `git status` `git diff` `git log` | `status/diff/log` |

+ | 7 | Stage | add | Add changes to the staging area | `git add -A` | `add` |

+ | 8 | Commit | commit | Package the staging area into a commit | `git commit -m "..."` | `commit` |

+ | 9 | Sync | fetch/pull/push | Fetch, merge, or push commits | `git fetch` `git pull` `git push` | `fetch/pull/push/push-main` |

+ |10| Merge | merge/rebase | Merge branch history | `git merge` `git rebase` | `merge/rebase` (use with caution) |

+ |11| Stash | stash | Temporarily set aside uncommitted changes | `git stash` | `stash` |

+ |12| Tag | tag | Add a version tag to a commit | `git tag` | `tag` |

+ |13| Submodule | submodule | Manage subrepository dependencies | `git submodule` | `submodule` |

+ |15| GitHub platform | issues/labels/milestones/releases/actions | Manage platform objects through the GitHub API | (API) | `gh-issues-list` and others (see below) |

+ > 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.

+ | No. | command | Purpose |

+ | 1 | `gh-issues-list --repo <owner/repo> [--state open|closed|all]` | List issues |

+ | 2 | `gh-issue-create --repo <owner/repo> --title <t> [--body <b>]` | Create an issue |

+ | 3 | `gh-issue-close --repo <owner/repo> --number <n>` | Close an issue |

+ | 4 | `gh-labels-list --repo <owner/repo>` | List labels |

+ | 5 | `gh-label-create --repo <owner/repo> --name <n> [--color <rrggbb>] [--description <d>]` | Create a label |

+ | 6 | `gh-milestones-list --repo <owner/repo> [--state open|closed|all]` | List milestones |

+ | 7 | `gh-milestone-create --repo <owner/repo> --title <t> [--description <d>] [--due <YYYY-MM-DD>]` | Create a milestone |

+ | 8 | `gh-releases-list --repo <owner/repo>` | List releases |

+ | 9 | `gh-release-create --repo <owner/repo> --tag <vX.Y.Z> --name <n> [--body <b>] [--draft true|false] [--prerelease true|false]` | Create a release |

+ |10| `gh-actions-list --repo <owner/repo>` | List workflows |

+ |11| `gh-actions-dispatch --repo <owner/repo> --workflow <id_or_file> [--ref <branch>] [--inputs <json>]` | Manually trigger workflow_dispatch |

+ ## Script Command List (gh_sync.sh)

+ | No. | command | Purpose |

+ | 2 | `clone --url <url> [--dir <path>]` | Clone a repository to a specified directory |

+ | 3 | `remotes` | Show current remotes |

+ | 4 | `add-remote --name <n> --url <url>` | Add a remote |

+ | 5 | `set-remote-url --name <n> --url <url>` | Change a remote URL |

+ | 6 | `remove-remote --name <n>` | Remove a remote |

+ | 7 | `add-upstream --upstream <owner/repo>` | Add the upstream remote |

+ | 8 | `status` | `git status --porcelain` + brief tips |

+ | 9 | `diff [--staged]` | View differences |

+ |10| `log [--n <k>]` | View recent commits |

+ |11| `branches` | List local and remote branches |

+ |12| `create-branch --name <b> [--from <ref>]` | Create a branch |

+ |13| `checkout --name <b>` | Switch branches |

+ |14| `delete-branches --keep <branch>` | Delete local/remote branches except the branch specified by `keep` |

+ |17| `fetch [--remote <n>]` | Fetch remote updates |

+ |18| `pull [--remote <n>] [--branch <b>]` | Pull and merge |

+ |19| `push [--remote <n>] [--branch <b>]` | Push |

+ |20| `push-main` | Push the current main branch to origin (using a token, non-interactive) |

+ |21| `empty-dir --dir <path>` | Empty a directory in the repository while preserving the directory (using .gitkeep) |

+ |22| `restore-dir --src <path> --dst <path>` | Restore to a repository directory by overwriting it with a local directory (deletes the contents of `dst` first) |

+ |23| `pr --upstream <owner/repo> --head <owner:branch> --base <branch> --title <t> --body <b>` | Create a PR through the GitHub API |

+ |24| `gh-issues-list ...` and others | GitHub platform object operations (issues/labels/milestones/releases/actions) |

+ ## Typical Workflows (Examples)

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

+ ### 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

+ # 2. Content-only overwrite: overwrite the target file in the repository with the source file contents

+ # 3. If the Git identity is not configured, prefer reusing the GitHub display name and GitHub noreply email

+ git config user.name '<GitHubDisplay Name>'

+ # 4. Commit and push directly to main (only when the user explicitly requests commit/push)

+ 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>'`

+ - 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)

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

+ - **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.

+ | No. | Symptom | Handling |

+ | 1 | push reports `could not read Username` | Requires env `GITHUB_TOKEN`; the script will use `GIT_ASKPASS` for non-interactive authentication |

+ | 2 | API 401/403 | Insufficient token permissions (repo/public_repo) or token expired |

+ | 3 | `not inside a git repo` | First `cd` to the repository directory (or use `clone`/`init`) |