nousresearch/hermes-agent

github

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

View source

See it in action

Usage example

Complete author template: a reproducible bug report

Full original Markdown template for reproduction steps, expected/actual behavior, environment and errors. Fill the blank fields and review logs before sharing; no real report, environment or public issue is supplied.

Example input

## Bug Description

<!-- Clear, concise description of the bug -->

## Steps to Reproduce

1.
2.
3.

## Expected Behavior

<!-- What should happen -->

## Actual Behavior

<!-- What actually happens -->

## Environment

- OS:
- Version/Commit:
- Python version:
- Browser (if applicable):

## Error Output

<!-- Paste relevant error messages, stack traces, or logs -->

```
```

## Additional Context

<!-- Screenshots, related issues, workarounds discovered, etc. -->
License

Complete original source unit, unchanged; outer Markdown fence omitted for a single block. Editorial title, context and prerequisites added. Placeholders and negative teaching content remain explicit; no source Skill, installation, account operation or claimed test outcome was executed.

MIT License

Copyright (c) 2025 Nous Research

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Usage example

Complete author template: a scoped feature request

Full original template connects motivation, proposed usage, alternatives and scope. Replace comments and placeholders with real requirements; the empty example fence is intentional template content, not a finished proposal.

Example input

## Feature Description

<!-- What do you want? -->

## Motivation

<!-- Why would this be useful? What problem does it solve? -->

## Proposed Solution

<!-- How could it work? Include API sketches, CLI examples, or mockups if helpful -->

```
# Example usage
```

## Alternatives Considered

<!-- Other approaches and why they're less ideal -->

-

## Scope / Effort Estimate

<!-- How big is this? What areas of the codebase would it touch? -->

Small / Medium / Large — <!-- explanation -->

## Additional Context

<!-- Links to similar features in other tools, relevant discussions, etc. -->
License

Complete original source unit, unchanged; outer Markdown fence omitted for a single block. Editorial title, context and prerequisites added. Placeholders and negative teaching content remain explicit; no source Skill, installation, account operation or claimed test outcome was executed.

MIT License

Copyright (c) 2025 Nous Research

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Usage example

Complete author template: explain and verify a bug fix

Full original PR body template covers cause, fix, review steps, test plan and risk. Fill Fixes # and factual evidence; unchecked regression and verification items are tasks to complete, not tests already passed.

Example input

## Bug Description

<!-- What was happening? -->

Fixes #

## Root Cause

<!-- What was causing the bug? -->

## Fix

<!-- What does this PR change to fix it? -->

-

## How to Verify

<!-- Steps a reviewer can follow to confirm the fix -->

1.
2.
3.

## Test Plan

- [ ] Added regression test for this bug
- [ ] Existing tests still pass
- [ ] Manual verification of the fix

## Risk Assessment

<!-- Could this fix break anything else? What's the blast radius? -->

Low / Medium / High — <!-- explanation -->
License

Complete original source unit, unchanged; outer Markdown fence omitted for a single block. Editorial title, context and prerequisites added. Placeholders and negative teaching content remain explicit; no source Skill, installation, account operation or claimed test outcome was executed.

MIT License

Copyright (c) 2025 Nous Research

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Usage example

Author review template: findings, severity and verdict

Complete original Markdown review summary including placeholders and the Reviewed by Hermes Agent footer. Fill it only after a real review, update attribution to the actual reviewer and use the parent severity guide; this is unfilled template text, not an approval or a review performed by the site.

Example input

## Code Review Summary

**Verdict: [Approved ✅ | Changes Requested 🔴 | Reviewed 💬]** ([N] issues, [N] suggestions)

**PR:** #[number] — [title]
**Author:** @[username]
**Files changed:** [N] (+[additions] -[deletions])

### 🔴 Critical
<!-- Issues that MUST be fixed before merge -->
- **file.py:line** — [description]. Suggestion: [fix].

### ⚠️ Warnings
<!-- Issues that SHOULD be fixed, but not strictly blocking -->
- **file.py:line** — [description].

### 💡 Suggestions
<!-- Non-blocking improvements, style preferences, future considerations -->
- **file.py:line** — [description].

### ✅ Looks Good
<!-- Call out things done well — positive reinforcement -->
- [aspect that was done well]

---
*Reviewed by Hermes Agent*
License

Complete original source unit, unchanged; outer Markdown fence omitted for a single block. Editorial title, context and prerequisites added. Placeholders and negative teaching content remain explicit; no source Skill, installation, account operation or claimed test outcome was executed.

MIT License

Copyright (c) 2025 Nous Research

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/nousresearch/hermes-agent --skill github

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

Related by task

from this repository

More skills

All skills