github-repo-management

Create, clone, fork, and configure GitHub repositories using gh CLI or REST API.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill github-repo-management-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/github/github-repo-management
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill github-repo-management-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyNaCl, and includes references (resource) components.

What problem does it solve? Managing GitHub repositories involves many repetitive operations—cloning, forking, creating repos, setting branch protection, managing secrets, and publishing releases—and doing them manually through the web UI or memorizing API endpoints is slow and error-prone. ## Core Features & Use Cases - Repository Lifecycle Management: Clone, create, fork, and sync repositories using the gh CLI with automatic git + curl fallbacks when gh is unavailable. - Configuration & Security: Edit repo settings, set branch protection rules, manage topics, and configure GitHub Actions secrets (including PyNaCl-based encryption for the API path). - Releases & CI Operations: Create releases with generated notes, upload assets, list and rerun workflow runs, download CI logs, and trigger workflow dispatches. - Use Case: You need to bootstrap a new open-source project: create a private repo from a template, push existing local code, protect the main branch with required CI checks, set an API key secret, and cut a v1.0.0 release—all from the terminal. ## Quick Start Ask the agent to create a new private GitHub repository named my-project, clone it locally, and enable branch protection on main.

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 --private --clone` with the GitHub CLI, or POST to `https://api.github.com/user/repos` with curl and an authorization token. Both approaches support descriptions, licenses, and organization-owned repos.

How to fork a repo and keep it in sync with upstream?▼

Fork with `gh repo fork owner/repo --clone`, then add the original as an upstream remote. Sync by fetching upstream, merging upstream/main into your main branch, and pushing, or use the `gh repo sync` shortcut.

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

Yes, every operation has a git plus curl fallback using the GitHub REST API with a GITHUB_TOKEN. The token can be loaded from the environment, a .env file, or git credentials. Secrets management is the one case where gh is strongly recommended.

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

Fetch the repository's public key from the actions/secrets/public-key endpoint, encrypt the secret value with PyNaCl SealedBox, then PUT the encrypted value to the secrets endpoint. Using `gh secret set` is dramatically simpler when available.

How do I rerun a failed GitHub Actions workflow?▼

Use `gh run rerun <RUN_ID>` or `gh run rerun <RUN_ID> --failed` for failed jobs only. Via the API, POST to `/repos/{owner}/{repo}/actions/runs/{run_id}/rerun` or the rerun-failed-jobs endpoint.

What are the GitHub API rate limits for repo management?▼

Authenticated requests allow 5,000 per hour. Check remaining quota with a GET to the rate_limit endpoint. List endpoints support pagination with per_page up to 100 and a page parameter.