GI

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.zip

Installs 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.
326 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

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

You give it
GitHub repository context and command parameters
You get back
Executed GitHub API action or CLI output

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:

TaskReference
Create, review, merge, close, compare, or converge PRs; clear approved PR body revisions; retire remote PR branchesreferences/pr_operations.md
Create, edit, search, transfer, close, or bulk-manage issuesreferences/issue_operations.md
Inspect, clone, create, edit, rename, archive, transfer, change visibility, or delete repositoriesreferences/repository_operations.md
Copy repositories accessible to another account while keeping the usual account active; configure private copies and upstream syncreferences/multi_account_repository_sync.md
Inspect or change collaborators, teams, base permissions, member privileges, or organization 2FAreferences/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 pushreferences/branch_protection.md
Trigger, inspect, approve a reviewed fork run, rerun, cancel, or purge Actions; diagnose missing checks; manage secrets or variablesreferences/workflow_operations.md
Reduce CI email overload, exhausted Actions allowance, unrelated checks or repeated runs; decide what a template or product actually needsreferences/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 hostsreferences/api_reference.md
Build scripts, retries, bulk operations, or machine-readable outputreferences/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:

  1. a purpose-built gh subcommand;
  2. a documented REST endpoint for one resource or authoritative readback;
  3. GraphQL when the required mutation/query is GraphQL-only or combines related data;
  4. 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

gh CLIGitHub account

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.

SkillInstallsUpdatedSafetyDifficulty
github-ops (this skill)15moReviewIntermediate
github-workflow-automation115moReviewAdvanced
testing-workflow161yReviewIntermediate
github-actions-templates77moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

ppt-creator

daymade

Create professional slide decks from topics or documents. Generates structured content with data-driven charts, speaker notes, and complete PPTX files. Applies persuasive storytelling principles (Pyramid Principle, assertion-evidence). Supports multiple formats (Marp, PowerPoint). Use for presentations, pitches, slide decks, or keynotes.

75110

macos-cleaner

daymade

Analyze and reclaim macOS disk space through intelligent cleanup recommendations. This skill should be used when users report disk space issues, need to clean up their Mac, or want to understand what's consuming storage. Focus on safe, interactive analysis with user confirmation before any deletions.

1631

qa-expert

daymade

This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.

1427

repomix-unmixer

daymade

Extracts files from repomix-packed repositories, restoring original directory structures from XML/Markdown/JSON formats. Activates when users need to unmix repomix files, extract packed repositories, restore file structures from repomix output, or reverse the repomix packing process.

524

teams-channel-post-writer

daymade

Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.

591

twitter-reader

daymade

Fetch Twitter/X post content by URL using jina.ai API to bypass JavaScript restrictions. Use when Claude needs to retrieve tweet content including author, timestamp, post text, images, and thread replies. Supports individual posts or batch fetching from x.com or twitter.com URLs.

552

You might also like

Search skills

Search the agent skills registry