github-repo-management

Manage GitHub repositories, remotes, secrets, releases, and workflows via gh CLI.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/zerwiz/wayofpi --skill github-repo-management-zerwiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/zerwiz/wayofpi/tree/main/.hermes/hermes-agent/skills/github/github-repo-management
Command: npx skills add https://github.com/zerwiz/wayofpi --skill github-repo-management-zerwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of day-to-day GitHub repository administration by giving you a single workflow for cloning, creating, forking, configuring, and operating repositories without switching tools.

Core Features & Use Cases

  • Repository Operations: Create, clone, fork, inspect, and configure GitHub repositories for new projects or existing codebases.
  • Automation and Release Management: Manage remotes, branch protection, secrets, releases, and GitHub Actions workflows for ongoing delivery.
  • Fallback-Friendly Workflow: Use gh when available for faster operations, or fall back to git plus the GitHub REST API for environments without gh.
  • Use Case: A developer can set up a new repository, publish a release, update secrets, and rerun a failed workflow from one repeatable operational playbook.

Quick Start

Ask the skill to manage a GitHub repository by describing the repository task you want completed, and it will choose gh first with git and curl fallbacks when needed.

Frequently Asked Questions about github-repo-management

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

FAQPage Schema
How do I manage GitHub repositories, secrets, and releases from the command line?

Managing GitHub repositories involves cloning, creating, configuring, and auditing them, plus operating secrets, releases, and Actions workflows, using a single workflow that chooses gh CLI first with git and curl fallbacks.

Do I need the GitHub CLI installed to automate GitHub Actions and repository tasks?

Automating GitHub Actions and repository tasks does not strictly require the GitHub CLI; the workflow applies gh first but supports fallbacks through standard git commands and the GitHub REST API via curl when gh is unavailable.

Can I configure branch protection and update repository secrets using curl?

Configuring branch protection and updating repository secrets using curl is supported by falling back to the GitHub REST API when the gh CLI is unavailable to execute the required repository configuration operations.

What is the best way to set up a new GitHub repository and publish a release?

Setting up a new GitHub repository and publishing a release is best achieved using a unified operational playbook that handles repository creation, remote management, and release publishing through gh with git and curl fallbacks.

Does this workflow support rerunning failed GitHub Actions workflows and managing gists?

The workflow supports operating GitHub Actions workflows, including rerunning failed jobs, and managing gists, providing a repeatable operational playbook for ongoing delivery and repository auditing tasks.