Github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

Skill metadata

Source	Bundled (installed by default)
Path	skills/software-development/github
Version	2.0.0
Author	Ben Barclay (benbarclay), Hermes Agent
License	MIT
Platforms	linux, macos, windows
Tags	github, gh, git, pull-requests, issues, code-review, repos, auth, ci
Related skills	codebase-inspection, requesting-code-review

Reference: full SKILL.md

信息

The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

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.