github-repo-management

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing GitHub repositories involves many repetitive operations—cloning, forking, creating repos, configuring settings, managing secrets, and publishing releases—that are tedious to perform manually through the web UI or to script from scratch. ## Core Features & Use Cases - Repository Lifecycle Management: Clone, create, fork, and sync repositories using either the gh CLI or git plus curl against the GitHub REST API, with automatic fallback when gh is unavailable. - Configuration & Automation: Edit repo settings, topics, branch protection rules, GitHub Actions secrets, and workflow runs programmatically. - Releases & Gists: Create releases with generated notes, upload binary assets, and manage gists. - Use Case: You need to bootstrap a new open-source project: create a private repo from a template, push existing local code, set branch protection on main, add CI secrets, and publish a v1.0.0 release—all from the terminal in one session. ## Quick Start Ask the agent to create a new private GitHub repository named my-project, clone it locally, and set up branch protection on the main branch.

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 send a POST request to https://api.github.com/user/repos with curl and an authorization token. Both approaches support descriptions, licenses, and organization ownership.

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

Fork with `gh repo fork owner/repo --clone` or POST to the /forks API endpoint, then add the original repo as an upstream remote. Sync by fetching upstream, merging upstream/main into your main branch, and pushing to origin.

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 come from the environment, a .env file, or git credentials. Only secrets encryption is notably harder without gh.

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

Retrieve the repo's public key from /actions/secrets/public-key, encrypt the secret value with PyNaCl SealedBox, then PUT the encrypted value to /actions/secrets/NAME. Using `gh secret set` is much simpler when available.

How do I rerun a failed GitHub Actions workflow?▼

Run `gh run rerun RUN_ID` or `gh run rerun RUN_ID --failed` for failed jobs only. With curl, POST to /repos/{owner}/{repo}/actions/runs/{run_id}/rerun or /rerun-failed-jobs.