github-repo-management

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

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill github-repo-management-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/github/github-repo-management
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill github-repo-management-kaminocorp

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, protecting branches, publishing releases, and debugging CI runs—that are tedious to perform manually through the web UI, especially when automating or working on remote machines. ## Core Features & Use Cases - Repository Lifecycle Management: Clone, create, fork, and configure repositories, including templates, topics, visibility, and branch protection rules. - Releases, Secrets, and CI: Create releases with assets, manage GitHub Actions secrets, list and rerun workflow runs, download CI logs, and trigger workflow dispatches. - Dual-Mode Operation: Every operation is shown with the gh CLI first and a git + curl REST API fallback, so it works even when gh is not installed. - Use Case: You need to fork an open-source project, keep it synced with upstream, set a branch protection rule requiring CI to pass, and publish a v1.0.0 release with auto-generated notes—all from a headless server without the gh CLI. ## Quick Start Use the github-repo-management skill to create a private repository named my-new-project, clone it locally, and protect its main branch.

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 my-project --public --clone` with the GitHub CLI. Without gh, send a POST request to https://api.github.com/user/repos with your token and a JSON body containing the name, description, and privacy setting, then clone or push to it with git.

How do I keep a forked GitHub repository in sync with upstream?▼

Add the original repository as an upstream remote, then run git fetch upstream, checkout main, merge upstream/main, and push to origin. With the gh CLI, `gh repo sync your-username/repo-name` performs the same sync in one command.

Can I manage GitHub repositories without the gh CLI installed?▼

Yes. Every operation has a fallback using git plus curl against the GitHub REST API with a GITHUB_TOKEN. The token can be extracted from ~/.git-credentials, and endpoints cover repos, forks, releases, secrets, and Actions workflows.

How do I set GitHub Actions secrets via the API?▼

Setting secrets via the REST API requires fetching the repository's public key, encrypting the value with PyNaCl's SealedBox, and sending a PUT request to /repos/{owner}/{repo}/actions/secrets/{name}. Using `gh secret set` is significantly simpler and recommended when available.

How do I rerun a failed GitHub Actions workflow from the terminal?▼

With gh, run `gh run rerun <RUN_ID>` or add --failed to rerun only failed jobs. Via the API, POST to /repos/{owner}/{repo}/actions/runs/{run_id}/rerun or /rerun-failed-jobs. You can also download run logs as a zip for debugging.

What are the GitHub REST API rate limits for authenticated requests?▼

Authenticated requests are limited to 5,000 per hour. You can check your remaining quota by sending a GET request to https://api.github.com/rate_limit with your authorization token.