Automate GitHub repository management and CI/CD monitoring via the gh CLI.

Install

mkdir -p .claude/skills/github-anhvu1107 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9674" && unzip -o skill.zip -d .claude/skills/github-anhvu1107 && rm skill.zip

Installs to .claude/skills/github-anhvu1107

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.

ALWAYS use this when the request matches Github: Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
130 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • PR status checking
  • CI failure debugging
  • Workflow run inspection
  • GitHub API querying

How it works

Interfaces with the GitHub API and CLI to manage PRs and inspect CI runs.

Inputs & outputs

You give it
Repository/PR identifier
You get back
CI status or API data

When to use github

  • Debug CI failures
  • Review pull requests
  • List GitHub actions workflows

About this skill

GitHub Skill

Selective Reading Rule

Start with:

  • references/senior-master-standard.md
  • references/usage-routing.md
  • references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

When to Use

  • When the user asks about GitHub issues, pull requests, workflow runs, or CI failures.
  • When you need gh issue, gh pr, gh run, or gh api from the command line.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

Debugging a CI Failure

Follow this sequence to investigate a failing CI run:

  1. Check PR status — identify which checks are failing:
    gh pr checks 55 --repo owner/repo
    
  2. List recent runs — find the relevant run ID:
    gh run list --repo owner/repo --limit 10
    
  3. View the failed run — see which jobs and steps failed:
    gh run view <run-id> --repo owner/repo
    
  4. Fetch failure logs — get the detailed output for failed steps:
    gh run view <run-id> --repo owner/repo --log-failed
    

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

When not to use it

  • Non-GitHub repository tasks
  • Complex repository administration

Prerequisites

GitHub CLI

Limitations

  • Requires GitHub CLI
  • Requires repository access

How it compares

Allows direct terminal-based interaction with GitHub workflows and API data.

Compared to similar skills

github side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
github (this skill)03moReviewIntermediate
github-workflow-automation112moReviewAdvanced
testing-workflow169moReviewIntermediate
github-actions-templates73moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

Search skills

Search the agent skills registry