Skip to content
TrustedSkillsbeta
Back to all skills

Github Ops

Listed
daymade·vlatest·backend·MIT

Automates GitHub repository management tasks like branch creation, merging, and issue labeling via simple commands.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add daymade/claude-code-skills --skill github-ops -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

daymade

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No credential access: failed

    Touches credential material in 1 place.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found

    • github-ops/references/multi_account_repository_sync.md:44SSH private keys or config
      IdentityFile ~/.ssh/id_ed25519_upstream
  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: api.github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.github.comsource host
  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned daymade/claude-code-skills at 1327636852.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
13 files, 3,931 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates GitHub repository management tasks using the gh CLI tool and GitHub REST/GraphQL APIs. It enables AI agents to perform actions such as creating, viewing, editing, and merging pull requests; managing issues and repository settings; interacting with GitHub Actions workflows; querying API endpoints; and automating various GitHub operations. This includes integration with GitHub Enterprise instances.

When to use it

  • Creating, viewing, editing, or merging pull requests
  • Managing GitHub issues or repository settings
  • Querying GitHub API endpoints (REST or GraphQL)
  • Working with GitHub Actions workflows
  • Performing bulk operations on repositories
  • Integrating with GitHub Enterprise
  • Automating GitHub operations via CLI or API

Key capabilities

  • Pull Request Management: Creation, viewing, merging (including squash merges), reviewing, and commenting. Supports bypassing JIRA enforcement checks using the "NOJIRA" prefix in PR titles.
  • Issue Management: Creation, listing, editing (adding labels), and closing issues.
  • Repository Operations: Viewing repository details, cloning repositories, creating new public repositories.
  • Workflow Management: Listing, running, watching, and downloading GitHub Actions workflows.
  • API Interaction: Direct access to GitHub REST API endpoints via the gh api command; supports GraphQL queries for complex operations.
  • Authentication & Configuration: Login (including GitHub Enterprise), status checks, setting default repositories, configuring gh settings, and managing output formats.
  • Output Formatting: Control output format using JSON to facilitate programmatic processing.

Example prompts

  • "Create a pull request titled 'NOJIRA: Fix typo in documentation' with the description 'Corrected a minor typographical error.'"
  • "List all open issues labeled as 'bug'."
  • "Run the workflow named 'deploy-to-production'."
  • "Get details for pull request number 123 via API."

Tips & gotchas

  • Authentication Required: The skill requires authentication with GitHub or GitHub Enterprise using gh auth login.
  • API Familiarity: Using the gh api command effectively may require some understanding of GitHub's REST and GraphQL APIs.
  • PR Title Conventions: PR titles should follow a specific convention: "GR-1234: Descriptive title" (with JIRA) or "NOJIRA: Descriptive title" (without JIRA).