Clone, create, fork repos; manage remotes, releases.
npx skills add https://github.com/HezaoHezao/poirot --skill github-repo-management
Create, clone, fork, configure, and manage GitHub repositories.
github-auth skill)# HTTPS
git clone https://github.com/owner/repo.git
# SSH
git clone [email protected]:owner/repo.git
# With gh (auto-forks if you don't have push access)
gh repo clone owner/repo
# Clone + set up remote for fork
gh repo clone owner/repo -- --origin upstream
git remote add origin https://github.com/$GH_USER/repo.git
# With gh (creates on GitHub + clones locally)
gh repo create my-project --public --clone --description "My project"
# Private
gh repo create my-project --private --clone
# With git + curl
mkdir my-project && cd my-project && git init
curl -s -X POST \
-H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/user/repos \
-d '{"name":"my-project","private":true,"description":"My project"}'
git remote add origin https://github.com/$GH_USER/my-project.git
git push -u origin main
# With gh (forks + clones + sets up remotes)
gh repo fork owner/repo --clone
# With curl
curl -s -X POST \
-H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/repos/owner/repo/forks
# Manual fork setup
git remote add upstream https://github.com/owner/repo.git
git remote set-url origin https://github.com/$GH_USER/repo.git
# List remotes
git remote -v
# Add remote
git remote add upstream https://github.com/owner/repo.git
# Change remote URL
git remote set-url origin [email protected]:owner/repo.git
# Remove remote
git remote remove upstream
# Sync fork with upstream
git fetch upstream
git checkout main
git merge upstream/main
git push origin main
# Create release with gh
gh release create v1.0.0 --title "v1.0.0" --notes "First stable release"
# Create release with assets
gh release create v1.0.0 ./dist/app.tar.gz ./dist/app.zip --title "v1.0.0"
# List releases
gh release list
# View release
gh release view v1.0.0
# Download release assets
gh release download v1.0.0 --pattern "*.tar.gz"
# With curl
curl -s -X POST \
-H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/repos/$OWNER/$REPO/releases \
-d '{"tag_name":"v1.0.0","name":"v1.0.0","body":"First stable release"}'
# With gh
gh repo edit --description "New description"
gh repo edit --enable-issues=false
gh repo edit --default-branch main
# With curl
curl -s -X PATCH \
-H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/repos/$OWNER/$REPO \
-d '{"description":"New description","default_branch":"main"}'
# With gh
gh secret set MY_SECRET --body "secret_value"
gh secret set MY_SECRET < secret_file.txt
gh secret list
gh secret delete MY_SECRET
# With curl (requires public key encryption)
# See https://docs.github.com/en/rest/actions/secrets
# With gh (requires --yes for confirmation)
gh repo delete owner/repo --yes
# With curl
curl -s -X DELETE \
-H "Authorization: token $GITHUB_TOKEN" \
https://api.github.com/repos/$OWNER/$REPO
private fork of a public repo (without enterprise).
create` auto-creates the tag if it doesn't exist.
public key. Use gh secret set instead of raw curl.
undone.
Add delays.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take hezaohezao/github-repo-management from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.