github-repo-management

Automate GitHub repository clone, fork, create, and configure tasks via gh CLI or git+curl.

228|35|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha --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/tree/main/hermes-agent/skills/github/github-repo-management
Command: npx skills add https://github.com/kaminocorp/hermes-alpha --skill github-repo-management-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clone, fork, create, and configure GitHub repositories with either the gh CLI or a Git-based REST approach, reducing manual setup steps and API overhead.

Core Features & Use Cases

  • Clone repositories locally with gh or git
  • Create new repositories (user or organization) with description and license
  • Fork existing repositories and keep forks in sync
  • Manage repository settings, topics, and secrets for GitHub Actions
  • Configure and trigger GitHub Actions workflows and releases

Quick Start

Authenticate with GitHub and start cloning, forking, or creating repositories using gh or git with curl.

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 cloning and forking GitHub repositories?

Automating GitHub repository management handles cloning and forking via the gh CLI or git with curl, reducing manual API overhead. It provisions repositories consistently for individual developers, teams, and organizations.

Can I configure GitHub Actions secrets and workflows without the web interface?

Configuring GitHub Actions secrets and workflows is fully supported via gh CLI or REST/curl fallbacks. You can manage repository settings, orchestrate workflows, and handle releases programmatically without manual web interaction.

Does this approach work for provisioning organization repositories at scale?

Provisioning organization repositories at scale works by applying consistent setup across user and organization accounts. It creates repositories with descriptions and licenses while maintaining metadata and secrets handling for teams.

What's the best way to keep forked repositories synced with upstream?

Keeping forked repositories synced is handled natively by the repository management automation. It forks existing repositories and maintains synchronization using either gh CLI commands or git-based REST approaches.

Do I need the gh CLI installed to manage repositories, or can I use git and curl?

You do not need the gh CLI exclusively; repository management supports both gh CLI and git with curl as a REST fallback. This dual approach ensures workflow setup and authentication succeed across different environments.