Infra, Ops & WorkflowAttention6969/100
Github (Nous Research)
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
ou envoie-le directement à ton agent.
Installer dans ton projet
Ce skill a un score de sûreté moyen. Vérifie le rapport avant de l’installer.
$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs github__nousresearch-hermes-agent__skills-software-development-10333abb6554Nous Research
NousResearch/hermes-agent
Contenu à copier
---
name: github
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:
origin: Nous Research
hermes:
tags: [github, gh, git, pull-requests, issues, code-review, repos, auth, ci]
category: software-development
related_skills: [codebase-inspection, requesting-code-review]
---
# 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.Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Github (Nous Research)
Preflight once per session: `gh auth status` — if it fails, go to
Prefer `gh` over raw REST; drop to `gh api` only for endpoints the
Never report CI green without checking `gh pr checks` yourself; never
Read full context before writing: `gh issue view --comments` /
Comment utiliser Github (Nous Research)
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Github (Nous Research)
Dis simplement à ton agent quelque chose comme :
Applique le skill github__nousresearch-hermes-agent__skills-software-development-10333abb6554 à cette tâche
Utilise github__nousresearch-hermes-agent__skills-software-development-10333abb6554 pour améliorer cette implémentation
Passe en revue ce sujet avec github__nousresearch-hermes-agent__skills-software-development-10333abb6554
Skills liés à Github (Nous Research)
Add CLI Command (.NET)
Add or change a dotnet CLI command, subcommand, or option across the relevant CLI projects. USE FOR: adding or changing a dotnet CLI command/subcommand, adding a new Option<T> or Argument<T>, registering a subcommand in the command tree, changing an option's help description or a command's runtime message, wiring a command parser, or updating --help output.Add Dotnet Aot Command (.NET)
Add, enable, or review a dotnet CLI command or feature in the Native AOT CLI (src/Cli/dotnet-aot) and prove its compatibility. USE FOR: migrating a command or option to AOT, reviewing an AOT migration PR, defining conservative eligibility and managed fallback, changing AotSourceFiles.props or AotDependencies.props, validating AOT/managed parity, NativeAOT-publishing tests, checking binary-size impact, or using the dn harness and separated SDK layout. DO NOT USE FOR: resolving IL trim/AOT analyzer warnings alone (use dotnet-aot-compat), running dotnet.Tests incrementally (use incremental-test), or pure managed CLI work.Add Net Analyzer (.NET)
Add, port, or change a .NET code analysis rule (CA####) under src/Microsoft.CodeAnalysis.NetAnalyzers. USE FOR: implementing a new CA analyzer and its code fixer, porting a rule or PR from the retired dotnet/roslyn-analyzers repo, allocating a diagnostic ID from DiagnosticCategoryAndIdRanges.txt, choosing RuleLevel/severity/category, wiring resx + xlf strings, recording the rule in AnalyzerReleases.Unshipped.md, regenerating the analyzer documentation/sarif files, and writing MSTest analyzer/code-fix tests with the VerifyCS/VerifyVB harness. DO NOT USE FOR: NETSDK#### MSBuild diagnostics (src/Tasks), CS####/BC#### compiler diagnostics or IDE#### analyzers (dotnet/roslyn), or CONTAINER#### diagnostics (src/Containers).