How do I install the Github skill?

Run npx skillmds@latest add anhvu1107/github 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 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?

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 free to use?

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

Who published Github?

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

Github by anhvu1107 — Agent Skill

Name: Github
Author: anhvu1107

File contents

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:

Check PR status — identify which checks are failing:
```
gh pr checks 55 --repo owner/repo
```
List recent runs — find the relevant run ID:
```
gh run list --repo owner/repo --limit 10
```
View the failed run — see which jobs and steps failed:
```
gh run view <run-id> --repo owner/repo
```
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.

---name: githubdescription: ALWAYS use this when the request matches Github: Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.---# GitHub Skill## Selective Reading RuleStart 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 RequestsCheck CI status on a PR:```bashgh pr checks 55 --repo owner/repo```List recent workflow runs:```bashgh run list --repo owner/repo --limit 10```View a run and see which steps failed:```bashgh run view <run-id> --repo owner/repo```View logs for failed steps only:```bashgh run view <run-id> --repo owner/repo --log-failed```### Debugging a CI FailureFollow this sequence to investigate a failing CI run:1. **Check PR status** — identify which checks are failing: ```bash gh pr checks 55 --repo owner/repo ```2. **List recent runs** — find the relevant run ID: ```bash gh run list --repo owner/repo --limit 10 ```3. **View the failed run** — see which jobs and steps failed: ```bash gh run view <run-id> --repo owner/repo ```4. **Fetch failure logs** — get the detailed output for failed steps: ```bash gh run view <run-id> --repo owner/repo --log-failed ```## API for Advanced QueriesThe `gh api` command is useful for accessing data not available through other subcommands.Get PR with specific fields:```bashgh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'```## JSON OutputMost commands support `--json` for structured output. You can use `--jq` to filter:```bashgh 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.

Frequently asked questions

Github