Individual skill
hermes-change-review
Use when a branch, pull request, Kanban task, or implementation must be reviewed separately for intent fidelity, repository quality, and verification evidence before completion or merge is accepted.
skills/hermes-change-review/SKILL.md
Source commit 367f8a35ff4703cec722b0678ad853814032ba7f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 127
- Repository last updated
- Oct 26, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- hermes-agent Repository topic
- open-source Repository topic
- python Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 3,120 bytesSKILL.mdcore · 7,651 bytesSKILL.mdcore · 7,651 bytesSKILL.mdcore · 7,651 bytesexamples/example-report.mddoc · 1,005 bytestests/cases.jsonasset · 1,668 bytestests/test_contracts.pyruns · 1,942 bytes
Read excerpt
# Hermes Change Review
## Overview
Review implementation work on three independent axes:
1. **Intent**: did the change build what was actually requested?
2. **Repository**: does the implementation fit the codebase's architecture, conventions, and safety boundaries?
3. **Verification**: what test, CI, build, or runtime evidence actually supports the completion claim?
Keep the axes separate. Clean code can implement the wrong thing. Correct behavior can arrive through poor architecture. A convincing diff can still be unverified.
## When to Use
Use this skill when: