/prismer-github

name: prismer-github
scope: coding
description: "GitHub via gh CLI: PRs, issues, reviews, repos, auth."
version: 2.0.0
author: Ben Barclay (benbarclay), Hermes Agent
license: MIT
platforms: [ linux, macos, windows ]
metadata:
  nativeReplaces: [ github ]
  hermes:
    tags: [ github, gh, git, pull-requests, issues, code-review, repos, auth, ci ]
    category: software-development
    related_skills: [ codebase-inspection, requesting-code-review ]
  requiresExplicitGrant: true

Prismer execution contract

This is the uniquely named `prismer-github` skill, adapted from Hermes. Use the actual tools exposed by the executing host; examples using terminal, process, delegate_task, vision_analyze or browser_* are not tool registrations. Missing dependencies do not hide this skill. Report command startup, version, account/permissions and task-specific live verification separately. Use task-owned artifact paths and existing user authorization; do not change shared accounts, Runtime/provider configuration, global security settings or unrelated work. See NOTICE.md and LICENSE for resource provenance. Runtime availability and upstream-entry suppression are owned by the integration layer.

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)

• Before use, resolve SKILL_ROOT to this installed directory and run

`python3 "$SKILL_ROOT/scripts/ensure-gh.py"`. Missing gh is automatically installed within existing host permissions, then version and auth are checked separately. Read `references/auth.md` for account and target repository permission gates.

• 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.