github-repo-management
Create and manage GitHub repositories, branches, commits, and PRs via local git commands and GitHub MCP. Use when the user asks to create a repo, push code, get repo info, manage branches, open PRs, or work with GitHub repositories.
How do I install this agent skill?
npx skills add https://github.com/fanthus/agent-skills --skill github-repo-managementIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides instructions for managing GitHub repositories using local git commands and GitHub MCP tools. It incorporates security best practices by explicitly forbidding the logging of secrets and requiring user confirmation before performing destructive actions such as force-pushing or deleting repositories and branches.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
1 file scanned · No issues
What does this agent skill do?
GitHub Repository Management
Rules
- Secrets: Do not echo, log, or include any token or secret in output, commands, or file contents. GitHub MCP handles auth.
- Destructive actions: Ask for confirmation before
git push --force,git branch -D, deleting a repo, or overwriting remote history. - Default branch: Prefer
main; usemasteronly when the repo already uses it. - Commits: Use Conventional Commits (e.g.
feat:,fix:,docs:).
Capabilities
- Run git commands locally (init, add, commit, push, branch, checkout, etc.).
- Operate on GitHub via GitHub MCP only: create repos, get repo info, list/create/merge PRs, manage branches. Do not use REST API or GITHUB_TOKEN directly.
Create a repo
When the user asks to "create a repo" or "create a GitHub repository":
-
Create on GitHub (GitHub MCP only):
- Use GitHub MCP
create_repository(or equivalent) withname, optionaldescription,private(default from user intent).
- Use GitHub MCP
-
Set origin locally (if already in a git repo):
git remote add origin https://github.com/<owner>/<repo>.gitIf
originexists and should point to the new repo, ask before changing it. -
If no local repo yet:
git init git remote add origin https://github.com/<owner>/<repo>.git -
First push (after at least one commit):
git push -u origin mainUse
mainunless the GitHub repo was created with a different default branch.
Push code
When the user asks to "push code" or "push to GitHub":
- Ensure git repo exists: Run
git status. If not a repo, ask whether togit initand set remote. - Check remote:
git remote -v. If noorigin, ask for repo URL or create repo first. - Commit cleanly:
git statusto see changes.- Stage:
git add <paths>orgit add -Aif user intends all changes. - Commit with a conventional message:
git commit -m "type(scope): description". - If there are uncommitted changes and user said "push", offer to commit first; do not force-push without asking.
- Push:
git push origin <branch>. Default branch ismain. If upstream not set:git push -u origin main.
Get repo info
When the user asks to "get repo info", "repo details", or "show repository":
- Identify repo: From
git remote get-url origin(owner/repo) or user-provided owner/name. - Fetch via GitHub MCP: Use MCP tools to get repository details (e.g. get repo, list branches, list PRs). Summarize: name, description, default branch, visibility, stars/forks if available, clone URL.
Branches
- Create branch:
git checkout -b <branch-name>then push:git push -u origin <branch-name>. - Switch branch:
git checkout <branch>orgit switch <branch>. - Delete branch: Local
git branch -d <branch>; remote delete only after user confirmation:git push origin --delete <branch>.
Pull requests
- Open PR: Use GitHub MCP to create a pull request (
head,basedefaultmain,title,body). - List PRs: Use GitHub MCP to list PRs; summarize by number, title, state, author.
- Merge: Use GitHub MCP to merge; confirm with user before merging.
Conventional commit messages
Use this format: type(scope): short description.
| Type | Use for |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no code change |
refactor | Code change, no feature/fix |
test | Adding or updating tests |
chore | Build, tooling, deps |
Examples:
feat(auth): add login endpointfix(api): correct date parsingdocs: update README setup steps
Summary checklist
- GitHub operations: GitHub MCP only (no REST API, no GITHUB_TOKEN in commands).
- Confirm before force push, branch delete, or repo delete.
- Default branch:
main. - All commits: conventional style.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/fanthus/agent-skills/github-repo-management">View github-repo-management on skillZs</a>