github-repo-management

Clone, create, fork, and configure GitHub repositories via CLI.

Updated May 16, 2026
One-click install
npx skills add https://github.com/jaredcroxton/hermes-mirror --skill github-repo-management-jaredcroxton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/jaredcroxton/hermes-mirror/tree/main/agents/skills/github/github-repo-management
Command: npx skills add https://github.com/jaredcroxton/hermes-mirror --skill github-repo-management-jaredcroxton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of repeatedly setting up and administering GitHub repositories (cloning, creating, forking, and configuring settings) without switching between different tools and commands.

Core Features & Use Cases

  • Repository lifecycle management: Clone existing repos, create new repos (including from templates), and fork repositories for collaboration or backups.
  • Remote and sync workflows: Add and manage remotes (e.g., upstream) and keep forks synchronized using either git commands or gh shortcuts.
  • Operational GitHub controls: Manage repository settings, branch protection, GitHub Actions workflows, releases, gists, and secrets (with safe guidance to avoid committing sensitive data).

Quick Start

Tell Hermes: "Manage my GitHub repository by cloning or creating it, then configure settings and branch protection for main using my authenticated credentials."

Frequently Asked Questions about github-repo-management

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

FAQPage Schema
How do I clone, create, and fork GitHub repositories from a single workflow?

You can manage GitHub repository lifecycles by cloning, creating, and forking repos without switching tools. The workflow handles remote synchronization, upstream tracking, and template-based repo creation to support backups or agent-mirror setups.

Can I manage GitHub Actions workflows and repository secrets without exposing credentials in commits?

Yes, you can control GitHub Actions workflows and administer repository secrets safely. The process operates against GitHub endpoints while enforcing safe guidance to prevent committing sensitive credentials or secrets directly into your repository history.

What is the best way to configure branch protection and repository settings on GitHub?

The best way to configure repository settings and branch protection is through authenticated GitHub access. Using `gh` or `git` with API token fallback, you can administer settings, manage releases, and enforce branch protection rules for main.

Do I need the `gh` CLI installed to automate GitHub repository management tasks?

No, you do not strictly need the `gh` CLI to automate GitHub repository management. The workflow supports `gh` but includes a `git` and API token fallback, requiring only authenticated GitHub access to perform actions against REST or CLI endpoints.

How do I keep a forked GitHub repository synchronized with its upstream remote?

To keep forked repositories synchronized, you can add and manage upstream remotes using either git commands or `gh` shortcuts. This sync workflow supports common developer environments and maintains alignment with the original repository.

Does this approach to repository management work for creating backups or agent-mirror setups?

Yes, this repository management approach explicitly supports backup and agent-mirror setups. By cloning, forking, and administering common repo operations through authenticated endpoints, you can automate repository configuration and lifecycle tasks across typical environments.