How do I install the Github skill?

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

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

Github by ekkolearnai — Agent Skill

Name: Github
Author: ekkolearnai

File contents

GitHub

Use gh for GitHub operations and git for local branches, commits, pulls, and pushes. Use code-reading tools for deep reviews.

Prerequisites

Check authentication before making a GitHub request:

gh auth status

If gh is missing or unauthenticated, explain what is required. Do not invent credentials or expose tokens.

Pull requests

gh pr list --repo owner/repo --json number,title,state,author,url
gh pr view 55 --repo owner/repo --json title,body,author,files,commits,reviews,reviewDecision
gh pr checks 55 --repo owner/repo
gh pr diff 55 --repo owner/repo
gh pr create --repo owner/repo --title "feat: title" --body-file /tmp/pr.md
gh pr merge 55 --repo owner/repo --squash

URLs work directly with commands such as gh pr view. Treat create, comment, review, merge, close, release, and workflow rerun operations as external mutations: perform them only when the user requested that action. Before submitting, show or verify the exact repository and target.

Issues

gh issue list --repo owner/repo --state open --json number,title,labels,url
gh issue view 42 --repo owner/repo --json title,body,comments,labels,state
gh issue create --repo owner/repo --title "Bug: ..." --body-file /tmp/issue.md
gh issue comment 42 --repo owner/repo --body-file /tmp/comment.md
gh issue close 42 --repo owner/repo --comment "Fixed in ..."

CI and runs

gh run list --repo owner/repo --limit 10
gh run view <run-id> --repo owner/repo --json status,conclusion,headSha,url
gh run view <run-id> --repo owner/repo --log-failed
gh run rerun <run-id> --repo owner/repo --failed

API

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
gh api repos/owner/repo/labels --jq '.[].name'
gh api --cache 1h repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}'

Prefer --json with --jq for structured output. Use --body-file for comments and bodies containing backticks, shell snippets, environment names, or user-provided text.

---name: githubdescription: Use GitHub CLI for repositories, issues, pull requests, reviews, CI runs, releases, and structured GitHub API queries.---# GitHubUse `gh` for GitHub operations and `git` for local branches, commits, pulls, and pushes. Use code-reading tools for deep reviews.## PrerequisitesCheck authentication before making a GitHub request:```bashgh auth status```If `gh` is missing or unauthenticated, explain what is required. Do not invent credentials or expose tokens.## Pull requests```bashgh pr list --repo owner/repo --json number,title,state,author,urlgh pr view 55 --repo owner/repo --json title,body,author,files,commits,reviews,reviewDecisiongh pr checks 55 --repo owner/repogh pr diff 55 --repo owner/repogh pr create --repo owner/repo --title "feat: title" --body-file /tmp/pr.mdgh pr merge 55 --repo owner/repo --squash```URLs work directly with commands such as `gh pr view`. Treat create, comment, review, merge, close, release, and workflow rerun operations as external mutations: perform them only when the user requested that action. Before submitting, show or verify the exact repository and target.## Issues```bashgh issue list --repo owner/repo --state open --json number,title,labels,urlgh issue view 42 --repo owner/repo --json title,body,comments,labels,stategh issue create --repo owner/repo --title "Bug: ..." --body-file /tmp/issue.mdgh issue comment 42 --repo owner/repo --body-file /tmp/comment.mdgh issue close 42 --repo owner/repo --comment "Fixed in ..."```## CI and runs```bashgh run list --repo owner/repo --limit 10gh run view <run-id> --repo owner/repo --json status,conclusion,headSha,urlgh run view <run-id> --repo owner/repo --log-failedgh run rerun <run-id> --repo owner/repo --failed```## API```bashgh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'gh api repos/owner/repo/labels --jq '.[].name'gh api --cache 1h repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}'```Prefer `--json` with `--jq` for structured output. Use `--body-file` for comments and bodies containing backticks, shell snippets, environment names, or user-provided text.

Frequently asked questions

Github