nousresearch/hermes-agent

github

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

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/nousresearch/hermes-agent --skill github

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

TaskRead first
Auth broken / new machine / token or SSH setup / gh loginreferences/auth.md
Create, triage, label, assign, close issuesreferences/issues.md
Branch, commit, open PR, watch CI, mergereferences/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, verdictreferences/code-review.md
Clone/create/fork repos, remotes, releasesreferences/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.

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills