github-repo-management

Manage GitHub repositories, releases, secrets, and workflows via gh CLI or REST API.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill github-repo-management-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/github/github-repo-management
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill github-repo-management-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing GitHub repositories involves many repetitive operations—cloning, forking, configuring settings, creating releases, and debugging CI runs—and doing them manually through the web UI is slow and hard to automate. This Skill provides ready-to-use commands for every common repository operation, with automatic fallback from the gh CLI to git plus curl when gh is unavailable. ## Core Features & Use Cases - Repository Lifecycle: Clone, create, fork, and sync repositories, including organization repos and template-based creation. - Configuration & Security: Edit repo settings, manage topics, set branch protection rules, and manage GitHub Actions secrets. - Releases & CI/CD: Create releases with assets, list and trigger workflows, rerun failed jobs, and download run logs. - Use Case: You need to fork an open-source project, keep it synced with upstream, set branch protection on main, and cut a v1.0.0 release with auto-generated notes—all from the terminal without opening a browser. ## Quick Start Ask the agent to clone a GitHub repository, fork it, or create a new release for your project using the gh CLI or curl fallback.

Frequently Asked Questions about github-repo-management

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

FAQPage Schema
How do I create a GitHub repository from the command line?

Use gh repo create with flags like --public, --private, --description, and --clone to create and clone in one step. Without gh, send a POST request with curl to https://api.github.com/user/repos including your token and a JSON body with the repo name and settings.

How do I fork a GitHub repo and keep it in sync?

Run gh repo fork owner/repo --clone, or POST to /repos/owner/repo/forks via the API and clone your copy. To sync, add the original as an upstream remote, then fetch upstream, merge upstream/main, and push to origin.

Can I manage GitHub repos without the gh CLI installed?

Yes, every operation has a git plus curl fallback using the GitHub REST API with a GITHUB_TOKEN. The token is read from the environment, ~/.hermes/.env, or ~/.git-credentials. Secrets management is the one case where gh is strongly recommended due to encryption complexity.

How do I set GitHub Actions secrets via the API?

Secrets must be encrypted with the repo's public key before uploading. Fetch the key from /actions/secrets/public-key, encrypt the value with PyNaCl's SealedBox, then PUT the encrypted payload to /actions/secrets/NAME. Using gh secret set is far simpler.

How do I rerun a failed GitHub Actions workflow?

Use gh run rerun RUN_ID, or add --failed to rerun only failed jobs. With curl, POST to /repos/owner/repo/actions/runs/RUN_ID/rerun or /rerun-failed-jobs. You can list recent runs first with gh run list or the /actions/runs endpoint.

What are the GitHub API rate limits for these operations?

Authenticated requests to the GitHub REST API allow 5,000 requests per hour. Check your remaining quota by sending a GET request to https://api.github.com/rate_limit with your authorization token.