github-repo-management

Create, clone, fork, and configure GitHub repositories using gh CLI or git with curl.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill github-repo-management-jamsdoescode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repo-management
Source: https://github.com/jamsdoescode/Erik-s-Portfolio/tree/main/openclicky/AppResources/OpenClicky/OpenClickyBundledSkills/github-repo-management
Command: npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill github-repo-management-jamsdoescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub repositories requires memorizing many CLI flags and REST API endpoints. This Skill provides ready-to-run commands for the full repository lifecycle, with both the gh CLI and a git + curl fallback when gh is unavailable. ## Core Features & Use Cases - Repository Lifecycle: Clone, create, fork, and sync repositories, including template-based creation and organization repos. - Configuration & Security: Edit repo settings, topics, branch protection rules, and manage GitHub Actions secrets. - Releases & CI: Create releases with assets, list and rerun workflow runs, trigger workflow dispatches, and manage gists. - Use Case: You need to fork an open-source project, keep it in sync with upstream, protect the main branch, and publish a v1.0.0 release with generated notes — all from the terminal without opening the GitHub website. ## Quick Start Ask the assistant to clone a GitHub repository, create a new private repo from your current directory, or set up branch protection on main using this skill.

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 with flags like --public, --private, --description, and --clone to create and clone in one step. Without gh, send a POST request to https://api.github.com/user/repos with your token, then git clone the new repo.

How do I fork a repo and keep it in sync with upstream?

Run gh repo fork owner/repo --clone, or POST to the /forks API endpoint and clone your copy. Add the original as an upstream remote, then run git fetch upstream, merge upstream/main, and push to origin, or use gh repo sync.

Can I manage GitHub repos without the gh CLI installed?

Yes, every operation has a git + curl fallback using the GitHub REST API with a GITHUB_TOKEN. The token can come from your 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 from the terminal?

Use gh secret set KEY --body value, which handles encryption automatically. Via the REST API you must fetch the repo's public key, encrypt the value with PyNaCl SealedBox, and PUT the encrypted payload, so gh is much simpler.

How do I rerun a failed GitHub Actions workflow?

Run gh run rerun RUN_ID, or add --failed to rerun only failed jobs. With curl, POST to /repos/OWNER/REPO/actions/runs/RUN_ID/rerun or /rerun-failed-jobs. You can list recent runs first with gh run list.

Why does GitHub API authentication fail with curl?

Requests fail when GITHUB_TOKEN is unset or lacks required scopes. The setup snippet checks gh auth status first, then falls back to reading the token from a .env file or ~/.git-credentials before making API calls.