github-ops
This tool uses the gh CLI and GitHub API to manage pull requests, issue trackers, and workflow actions.
Install
mkdir -p .claude/skills/github-ops && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3896" && unzip -o skill.zip -d .claude/skills/github-ops && rm skill.zipInstalls to .claude/skills/github-ops
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Provides comprehensive GitHub operations using gh CLI and GitHub API. Activates when working with pull requests, issues, repositories, workflows, or GitHub API operations including creating/viewing/merging PRs, managing issues, querying API endpoints, and handling GitHub workflows in enterprise or public GitHub environments.Key capabilities
- →Manage pull requests via CLI
- →Perform issue tracking operations
- →Interact with GitHub Actions workflows
- →Query GitHub REST and GraphQL APIs
- →Configure authentication and repository settings
How it works
The skill utilizes the gh CLI tool to interface with GitHub's REST and GraphQL APIs, allowing for automated management of repository resources and workflows.
Inputs & outputs
When to use github-ops
- →Reviewing and merging pull requests from the terminal
- →Creating and editing GitHub issues
- →Querying GitHub API endpoints
- →Managing GitHub Action workflows
About this skill
GitHub Operations
Deliver the requested GitHub state, not a successful-looking command. A 200, 201,
202, or 204 response is evidence that GitHub accepted a request; it is not proof
that every requested field changed, an invitation was accepted, an asynchronous job
finished, or the user's business outcome was achieved.
Route by operation
Read only the reference required for the task:
| Task | Reference |
|---|---|
| Create, review, merge, close, compare, or converge PRs; clear approved PR body revisions; retire remote PR branches | references/pr_operations.md |
| Create, edit, search, transfer, close, or bulk-manage issues | references/issue_operations.md |
| Inspect, clone, create, edit, rename, archive, transfer, change visibility, or delete repositories | references/repository_operations.md |
| Copy repositories accessible to another account while keeping the usual account active; configure private copies and upstream sync | references/multi_account_repository_sync.md |
| Inspect or change collaborators, teams, base permissions, member privileges, or organization 2FA | references/organization_access_and_settings.md |
| Protect a default branch while letting collaborators contribute through PRs; inventory protection gaps across an account, roll a baseline out to many repositories, and verify enforcement with a real push | references/branch_protection.md |
| Trigger, inspect, approve a reviewed fork run, rerun, cancel, or purge Actions; diagnose missing checks; manage secrets or variables | references/workflow_operations.md |
| Reduce CI email overload, exhausted Actions allowance, unrelated checks or repeated runs; decide what a template or product actually needs | references/ci-demand-and-notifications.md before changing runners or notifications |
| Build and publish a Docker/OCI image to GitHub Container Registry (GHCR) | references/ghcr_publishing.md |
| Use raw REST/GraphQL endpoints, pagination, rate limits, webhooks, or Enterprise hosts | references/api_reference.md |
| Build scripts, retries, bulk operations, or machine-readable output | references/best_practices.md |
For local Git recovery, dirty worktrees, bundles, or lost commits, use git-safety-net.
This skill owns GitHub-hosted state.
For repository copies, also handle per-remote authentication and sync setup.
Universal operating contract
1. Classify the request before touching GitHub
- Answer, inspect, diagnose, or review: read-only. Do not create a PR, issue, comment, invitation, workflow run, or setting change.
- Create, change, merge, close, grant, revoke, publish, or delete: the named state change is authorized. Keep the target and blast radius inside that request.
- Destructive, public, credential-related, production-triggering, or externally communicative: require the exact target, consequence, and recovery path. If the user did not provide a material choice such as repository owner, visibility, or message content, stop before the write.
Do not turn a read-only investigation into a mutation because the fix looks obvious. Do not send a comment, review, issue, or invitation whose recipient or content was not authorized in the current task.
For an authorized contributor, assess repository access against their ongoing contribution role, not just today's read or sync command. Repository Write access and permission to update the default branch are separate decisions. Follow the user's chosen contribution scope; use branch protection and PR review to control integration rather than silently reducing a contributor to Read. A diagnosis alone still does not authorize a grant.
2. Bind identity, host, and target
Before the first write, verify the active account and resolve a fully qualified target:
gh auth status --hostname HOST
gh api --hostname HOST user --jq '.login'
gh repo view HOST/OWNER/REPO \
--json nameWithOwner,visibility,isPrivate,viewerPermission,url
For github.com, OWNER/REPO is sufficient. Never use gh auth status --show-token
for routine diagnosis, and never print, paste, or log a token.
Before the first push to a remote in the current session, read its live visibility:
gh repo view OWNER/REPO \
--json nameWithOwner,visibility,isPrivate,stargazerCount,forkCount,url
Bind identity to the interface that will perform the write. CLI identity does not establish a connector, browser, REST client, or Git SSH identity. Resolve the expected actor from the user's authorized task; neither the repository owner nor an available credential selects that actor automatically. For connectors, use a read-only current-user operation from that same connector and confirm its actor. If that interface cannot expose the actor, use the already verified CLI channel for the authorized write; do not make a test comment to discover its identity.
For authorized gh API/hosted-state writes, use the bundled checked invocation.
Resolve <github-ops-dir> to the directory containing this SKILL.md; run the
helper by that path from the task's working directory. Its executable argument
and rejection contract is checked_gh.py.
uv run python <github-ops-dir>/scripts/checked_gh.py --expected-login <EXPECTED_LOGIN> --host HOST
uv run python <github-ops-dir>/scripts/checked_gh.py --expected-login <EXPECTED_LOGIN> --host HOST -- pr edit <NUMBER> -R OWNER/REPO --title '<AUTHORIZED_TITLE>'
The first command is read-only. The second resolves the current credential,
checks GET /user, and pins that same credential for one command. A mismatch or
unknown actor exits before execution. It guards only gh, not connector calls,
browser actions or Git pushes. Authentication/configuration commands are rejected;
task authorization, exact targets and independent readback remain required.
Supply -R OWNER/REPO for repository-scoped commands, or an explicit repository
operand for gh repo. The wrapper qualifies that target with the checked host,
removes inherited GH_REPO and alternate token variables from the child, and
rejects conflicting host operands. Omit the command for an identity-only read.
Organization secret/variable operations instead use their explicit --org
scope; personal Codespaces secrets use --user. Body/title/field values remain
unchanged even when they resemble flags or URLs. Public API absolute URLs use
api.github.com; relative API endpoints remain supported.
For PR merges, use the checked pr merge entry with an explicit PR and full
--match-head-commit. It checks the live head and effective approval/merge state.
Raw REST and GraphQL PR merge writes are rejected: an eligible actor can otherwise
use bypass privileges without an --admin argument. Follow the
merge and explicit-bypass contract.
Switching account, credential, host or interface invalidates earlier identity
evidence. Recheck before the next write; do not reuse a prior session's pass.
Reference examples show native gh operation syntax. Execute hosted-state
mutations by passing those arguments after the helper's --, with an explicit
repository or account scope; bare gh remains suitable for readback and
separately authorized authentication/configuration. When a builtin's operand
shape is rejected, use its supported explicit REST/GraphQL equivalent through
the same helper, except PR merge writes, which stay on the guarded pr merge
entry. Do not bypass the actor check. A failed or timed-out invocation
does not prove the mutation was absent: read the exact target before retrying.
For incident attribution, preserve event ID/time, actor and interface separately
from the ChatGPT execution account. A comment author's login and
performed_via_github_app establish GitHub actor/application, not the ChatGPT
email. A session's creator identity and today's auth file do not establish its
historical execution account. Keep missing links unknown.
3. Read current authority and preview the delta
Use GitHub-hosted state, not a stale local ref or remembered setting. Capture only the fields required to prove the requested transition. Before a consequential write, make this plan explicit:
Target: fully qualified repository, organization, PR, issue, run, or account
Current: authoritative fields and immutable IDs/SHAs
Requested: exact field or state transition
Blast radius: people, repositories, forks, runs, or public surfaces affected
Recovery: exact inverse operation or explicit “not recoverable”
Readback: independent GET/CLI query and expected result
If the user already authorized this exact consequence, execute it. Do not add a ceremonial second confirmation. If target, scope, public exposure, deletion, recipient, or recovery remains ambiguous, pause before the write.
4. Choose an interface whose input contract actually supports the change
Prefer, in order:
- a purpose-built
ghsubcommand; - a documented REST endpoint for one resource or authoritative readback;
- GraphQL when the required mutation/query is GraphQL-only or combines related data;
- the documented GitHub UI when the setting has no supported API input.
Response fields are not automatically writable fields. Before using PATCH, compare
the desired key against the operation's current request body parameters, not the
shape returned by GET. GitHub may ignore an unsupported key while still returning a
successful response. Do not switch API families merely to make the command run.
Use explicit methods with
Content truncated.
When not to use it
- →Tasks unrelated to GitHub platform operations
- →Direct manipulation of local git history without GitHub context
Prerequisites
Limitations
- →Requires active network connection to GitHub
- →Subject to GitHub API rate limits
How it compares
Unlike manual browser-based management, this skill enables programmatic control and automation of GitHub tasks directly from the terminal.
Compared to similar skills
github-ops side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| github-ops (this skill) | 1 | 5mo | Review | Intermediate |
| github-workflow-automation | 11 | 5mo | Review | Advanced |
| testing-workflow | 16 | 1y | Review | Intermediate |
| github-actions-templates | 7 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by daymade
View all by daymade →You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
create-pr
n8n-io
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.