github-sync-helper

Automates Git operations and GitHub API workflows for issues, releases, and pull requests.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/riipandi/minis-skills --skill github-sync-helper-riipandi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-sync-helper
Source: https://github.com/riipandi/minis-skills/tree/main/github-sync-helper
Command: npx skills add https://github.com/riipandi/minis-skills --skill github-sync-helper-riipandi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Managing Git repositories and GitHub platform objects requires memorizing dozens of commands and API calls, and repetitive sync workflows like pushing to main, creating PRs, or managing issues are error-prone when done manually. ## Core Features & Use Cases - Git Command Automation: Run init, clone, branch, commit, push, pull, stash, tag, and submodule operations through a single script with numbered, table-formatted output. - GitHub Platform API Operations: Create and list issues, labels, milestones, releases, and trigger GitHub Actions workflows using the GITHUB_TOKEN environment variable. - Safe Sync Workflows: Perform one-click directory restore-and-push, fork-to-upstream PR creation, and branch cleanup with confirmation guards for dangerous operations. - Use Case: Sync a local skill directory into a GitHub repo by emptying the target directory, restoring content from local, committing, and pushing to main with non-interactive token authentication. ## Quick Start Ask the assistant to clone a GitHub repository, commit your local changes, and push them to main using the github-sync-helper script.

Frequently Asked Questions about github-sync-helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push to GitHub main branch non-interactively from a script?

Use the push-main command, which authenticates via the GITHUB_TOKEN environment variable and a GIT_ASKPASS helper so no username or password prompt appears. The script requires a --yes confirmation flag because pushing to main is a dangerous operation.

How to create a GitHub pull request from a fork using the API?

Run the pr command with --upstream set to the target owner/repo, --head as your fork owner:branch, and --base as the target branch. The script calls the GitHub pulls API endpoint with your GITHUB_TOKEN and returns the PR URL.

What permissions does the GitHub token need for issues and releases?

The token needs repo scope (or public_repo for public repositories) to create issues, labels, milestones, and releases through the API. HTTP 401 or 403 responses indicate insufficient token permissions or an expired token.

Why does git push fail with could not read Username?

This error occurs when git cannot prompt for credentials in a non-interactive shell. The script solves it by setting GIT_ASKPASS to a helper that supplies the GITHUB_TOKEN and disabling terminal prompts with GIT_TERMINAL_PROMPT=0.

Can I delete all branches except main in one command?

Yes, the delete-branches command with --keep main removes all other local branches and deletes the corresponding remote branches on origin. It requires the --yes flag to confirm since branch deletion is hard to reverse.