github-repo-management

Automate GitHub repository management using gh and REST API.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill github-repo-management-chris-chai-minjae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge/tree/main/skills/github/github-repo-management
Command: npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill github-repo-management-chris-chai-minjae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates GitHub repository management using gh and REST API, reducing manual setup work across multiple repos.

Core Features & Use Cases

  • Create, clone, fork, configure, and manage repositories across user and organization scopes.
  • Manage remotes, secrets, releases, and GitHub Actions workflows.
  • Supports gh CLI first, with a git + curl fallback for environments without gh.

Quick Start

Create a new repository with gh, configure its default remote, and push your initial commit.

Frequently Asked Questions about github-repo-management

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

FAQPage Schema
How do I automate GitHub repository management across multiple repos?

Automate GitHub repository management by using the gh CLI or curl with the REST API to clone, create, fork, and configure repos. This reduces manual setup work across user and organization scopes.

Can I manage GitHub Actions workflows and secrets via the command line?

Yes, you can manage GitHub Actions workflows and secrets via the command line. The Skill uses gh CLI and REST API calls to configure, update, and manage these resources across your repositories.

Do I need the gh CLI to manage GitHub repos, or can I use curl?

You do not need the gh CLI if you have curl. The Skill supports gh CLI first, but provides a git and curl fallback requiring a valid GITHUB_TOKEN for authenticated REST API operations.

What's the best way to create a new repository and configure its default remote?

The best way to create a new repository and configure its default remote is using the gh CLI. You can then push your initial commit directly through automated command line operations.

Does this approach work for managing both user and organization GitHub repositories?

Yes, this approach works for managing both user and organization GitHub repositories. It supports creating, cloning, forking, and configuring remotes, secrets, releases, and workflows across both scopes.

Why use a REST API fallback for GitHub repository automation?

Use a REST API fallback for GitHub repository automation in environments without the gh CLI installed. It requires curl and a valid GITHUB_TOKEN to execute authenticated operations.