How do I install the Github skill?

Run npx skillmds@latest add wundercorp/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.

What does the Github skill do?

GitHub via gh CLI: PRs, issues, reviews, repos, auth. It is listed under Coding & Dev Tools on SkillMD.

Is Github safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, reads secrets. 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. This skill is licensed under MIT.

Who published Github?

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

Github by wundercorp — Agent Skill

Name: Github
Rating: 4.2 (5 reviews)
Author: wundercorp

File contents

GitHub

Work GitHub end to end with the gh CLI (REST fallback where noted): auth, issues, the PR lifecycle, issue-to-PR delivery, code review, and repo management. This skill consolidates six former skills; each workflow lives complete in its reference file — ALWAYS read the matching reference before starting that workflow, the body below only routes.

Routing

Task	Read first
Auth broken / new machine / token or SSH setup / gh login	`references/auth.md`
Create, triage, label, assign, close issues	`references/issues.md`
Branch, commit, open PR, watch CI, merge	`references/pr-workflow.md`
Carry an ISSUE to a verified PR (full delivery loop)	`references/issue-to-pr.md`
Review someone's PR: diffs, inline comments, verdict	`references/code-review.md`
Clone/create/fork repos, remotes, releases	`references/repo-management.md`

Supporting assets: scripts/gh-env.sh + scripts/git-credential-token.py (auth helpers), templates/ (PR bodies, bug report, feature request), references/ci-troubleshooting.md, references/conventional-commits.md, references/github-api-cheatsheet.md, references/review-output-template.md.

Core discipline (applies to every workflow)

Preflight once per session: gh auth status — if it fails, go to references/auth.md before anything else.
Prefer gh over raw REST; drop to gh api only for endpoints the porcelain lacks (the cheatsheet lists them).
Never report CI green without checking gh pr checks yourself; never claim merged without verifying state,mergedAt.
Read full context before writing: gh issue view --comments / gh pr view --comments — decisions live in threads, not titles.
Sweep for duplicates before creating anything: gh pr list --search / gh issue list --search.

Verification

The workflow's own reference file defines done for that task.
Cross-cutting: every claim about remote state (CI, merge, release, issue state) is backed by a fresh gh read, never memory.

---name: githubdescription: "GitHub via gh CLI: PRs, issues, reviews, repos, auth."version: 2.0.0author: Ben Barclay (benbarclay), Loki Agentlicense: MITplatforms: [linux, macos, windows]metadata: loki: tags: [github, gh, git, pull-requests, issues, code-review, repos, auth, ci] category: software-development related_skills: [codebase-inspection, requesting-code-review]---# GitHubWork GitHub end to end with the `gh` CLI (REST fallback where noted): auth,issues, the PR lifecycle, issue-to-PR delivery, code review, and repomanagement. This skill consolidates six former skills; each workflow livescomplete in its reference file — ALWAYS read the matching reference beforestarting that workflow, the body below only routes.## Routing| Task | Read first ||---|---|| Auth broken / new machine / token or SSH setup / gh login | `references/auth.md` || Create, triage, label, assign, close issues | `references/issues.md` || Branch, commit, open PR, watch CI, merge | `references/pr-workflow.md` || Carry an ISSUE to a verified PR (full delivery loop) | `references/issue-to-pr.md` || Review someone's PR: diffs, inline comments, verdict | `references/code-review.md` || Clone/create/fork repos, remotes, releases | `references/repo-management.md` |Supporting assets: `scripts/gh-env.sh` + `scripts/git-credential-token.py`(auth helpers), `templates/` (PR bodies, bug report, feature request),`references/ci-troubleshooting.md`, `references/conventional-commits.md`,`references/github-api-cheatsheet.md`, `references/review-output-template.md`.## Core discipline (applies to every workflow)- Preflight once per session: `gh auth status` — if it fails, go to `references/auth.md` before anything else.- Prefer `gh` over raw REST; drop to `gh api` only for endpoints the porcelain lacks (the cheatsheet lists them).- Never report CI green without checking `gh pr checks` yourself; never claim merged without verifying `state,mergedAt`.- Read full context before writing: `gh issue view --comments` / `gh pr view --comments` — decisions live in threads, not titles.- Sweep for duplicates before creating anything: `gh pr list --search` / `gh issue list --search`.## Verification- The workflow's own reference file defines done for that task.- Cross-cutting: every claim about remote state (CI, merge, release, issue state) is backed by a fresh `gh` read, never memory.

Frequently asked questions

Github