How do I install the Github Operations skill?

Run npx skillmds@latest add s3yed/github-operations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Operations safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Operations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Operations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Operations?

S3YED (@s3yed) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Operations by s3yed — Agent Skill

Name: Github Operations
Author: S3YED

Github Operations

Operate GitHub end to end with git, gh CLI, and REST: authentication, repository management, issues, pull requests, CI monitoring, code review, releases, labels, secrets, and project triage. Use for any GitHub workflow instead of loading narrow GitHub subskills separately.

S3YED 9155ba5 3.2 KB Updated Sep 17, 2026

File contents

GitHub Operations

Use this umbrella for GitHub work. Prefer gh when authenticated and available; fall back to plain git plus REST API calls when gh is missing or the environment is headless.

Start every workflow with discovery

git remote -v
gh auth status || true
gh repo view --json nameWithOwner,defaultBranchRef || true

Extract owner/repo from origin when gh is unavailable. Do not assume the current directory is the target repository.

Authentication

Choose the least-friction method that fits the host:

Existing gh login: use gh auth status and gh api.
Headless gh auth login --with-token when the user provides a token.
Plain Git HTTPS with a credential helper or token-embedded remote when gh is unavailable.
SSH keys for persistent developer machines.

Reusable shell helpers from the old auth/code-review skills live in scripts/gh-env.sh when present.

Repository management

Use for cloning, creating, forking, remotes, releases, secrets, settings, and repository metadata. See references/github-api-cheatsheet.md for REST endpoint patterns.

Common operations:

gh repo clone OWNER/REPO
gh repo create NAME --private --clone
gh repo fork OWNER/REPO --clone
gh release create v1.2.3 dist/* --notes "..."

Issues

Use issues for bug reports, feature requests, triage, labels, milestones, and assignment.

gh issue list --state open
gh issue view 123 --comments
gh issue create --title "..." --body-file body.md
gh issue edit 123 --add-label bug --add-assignee @me

Templates are available under templates/bug-report.md and templates/feature-request.md.

Pull request lifecycle

Sync default branch.
Create a focused branch.
Commit with a conventional message.
Push and open a PR with a clear body and test plan.
Monitor checks and fetch logs for failures.
Fix CI, update the branch, and merge only when policy allows.

Templates and references:

templates/pr-body-feature.md
templates/pr-body-bugfix.md
references/ci-troubleshooting.md
references/conventional-commits.md

Code review

Review local diffs or GitHub PRs for correctness, regressions, security, tests, and maintainability. Load references/review-output-template.md for the preferred report shape.

gh pr view PR --json title,body,author,baseRefName,headRefName
gh pr diff PR
gh pr checkout PR

Verify every finding against code and tests before posting comments. Prefer one summary review over noisy inline comments unless line-specific context matters.

Safety rules

Ask before pushing, force-pushing, merging, deleting branches, changing repo settings, or posting public comments unless the user explicitly requested that action.
Never print or store tokens in logs. Use env vars or gh auth login --with-token.
For destructive repo operations, capture the target owner/repo and branch in the final confirmation.

---name: github-operationsdescription: Operate GitHub end to end with git, gh CLI, and REST: authentication, repository management, issues, pull requests, CI monitoring, code review, releases, labels, secrets, and project triage. Use for any GitHub workflow instead of loading narrow GitHub subskills separately.---# GitHub OperationsUse this umbrella for GitHub work. Prefer `gh` when authenticated and available; fall back to plain `git` plus REST API calls when `gh` is missing or the environment is headless.## Start every workflow with discovery```bashgit remote -vgh auth status || truegh repo view --json nameWithOwner,defaultBranchRef || true```Extract owner/repo from `origin` when `gh` is unavailable. Do not assume the current directory is the target repository.## AuthenticationChoose the least-friction method that fits the host:1. Existing `gh` login: use `gh auth status` and `gh api`.2. Headless `gh auth login --with-token` when the user provides a token.3. Plain Git HTTPS with a credential helper or token-embedded remote when `gh` is unavailable.4. SSH keys for persistent developer machines.Reusable shell helpers from the old auth/code-review skills live in `scripts/gh-env.sh` when present.## Repository managementUse for cloning, creating, forking, remotes, releases, secrets, settings, and repository metadata. See `references/github-api-cheatsheet.md` for REST endpoint patterns.Common operations:```bashgh repo clone OWNER/REPOgh repo create NAME --private --clonegh repo fork OWNER/REPO --clonegh release create v1.2.3 dist/* --notes "..."```## IssuesUse issues for bug reports, feature requests, triage, labels, milestones, and assignment.```bashgh issue list --state opengh issue view 123 --commentsgh issue create --title "..." --body-file body.mdgh issue edit 123 --add-label bug --add-assignee @me```Templates are available under `templates/bug-report.md` and `templates/feature-request.md`.## Pull request lifecycle1. Sync default branch.2. Create a focused branch.3. Commit with a conventional message.4. Push and open a PR with a clear body and test plan.5. Monitor checks and fetch logs for failures.6. Fix CI, update the branch, and merge only when policy allows.Templates and references:- `templates/pr-body-feature.md`- `templates/pr-body-bugfix.md`- `references/ci-troubleshooting.md`- `references/conventional-commits.md`## Code reviewReview local diffs or GitHub PRs for correctness, regressions, security, tests, and maintainability. Load `references/review-output-template.md` for the preferred report shape.```bashgh pr view PR --json title,body,author,baseRefName,headRefNamegh pr diff PRgh pr checkout PR```Verify every finding against code and tests before posting comments. Prefer one summary review over noisy inline comments unless line-specific context matters.## Safety rules- Ask before pushing, force-pushing, merging, deleting branches, changing repo settings, or posting public comments unless the user explicitly requested that action.- Never print or store tokens in logs. Use env vars or `gh auth login --with-token`.- For destructive repo operations, capture the target owner/repo and branch in the final confirmation.

Frequently asked questions