hermes-repo-devsetup

Provisions repositories with repo-local Hermes profiles, hook scripts, and dev entrypoints.

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/harlanljones/dotfiles --skill hermes-repo-devsetup-harlanljones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-repo-devsetup
Source: https://github.com/harlanljones/dotfiles/tree/main/dot_hermes/skills/devops/hermes-repo-devsetup
Command: npx skills add https://github.com/harlanljones/dotfiles --skill hermes-repo-devsetup-harlanljones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a consistent, repo-local Hermes agent environment (profile, pruned skills, hook scripts, rules files, and a ./dev entrypoint) is error-prone, with subtle pitfalls like corrupted config values, untrusted skills, and silently non-executing hooks. ## Core Features & Use Cases - Exemplar Mirroring: Reads an established reference repo (~/dev/verdict) first, then mirrors its dev script, profile config, and hook structure adapted to the new repo's language and toolchain. - Profile & Hook Provisioning: Creates Hermes profiles, prunes skills via literal JSON config sets, and installs git-guard, formatter, and evidence-recorder hook scripts with correct event registration. - Verification & Pitfall Avoidance: Ships a doctor command that validates profile, skill symlinks, trust counts, hook executability, and toolchain presence, plus a catalog of known failure modes and their fixes. - Use Case: When starting a new web project, run this procedure to clone the verdict setup, swap the cargo-fmt hook for prettier/eslint, and finish with a passing ./dev doctor before committing. ## Quick Start Set up a repo-local Hermes dev environment for this repository by mirroring the verdict exemplar, then verify it with ./dev doctor.

Frequently Asked Questions about hermes-repo-devsetup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a repo-local Hermes profile for a new repository?▼

Create the profile with hermes profile create <name> --clone, prune skills via config set with a literal JSON array, install hook scripts, then add a ./dev entrypoint that ensures setup and execs hermes --profile <name>. Mirror an existing exemplar repo first.

How do I configure Hermes hooks for a profile?▼

Place executable scripts in ~/.hermes/agent-hooks/ and register them with hermes -p <name> config set hooks.<event> '<JSON array>' --force. Scripts read a JSON payload from stdin and must print {} on no-op; pre_tool_call blocks via exit 2.

Why does hermes config set fail with unrecognized arguments?▼

The working form is hermes -p <name> config set <key> '<literal JSON>' --force, with --force after the value and -p before the subcommand. Putting --force before the value triggers the unrecognized arguments error.

Why does hermes skills trust report not inside a git checkout?▼

skills trust does not resolve the enclosing checkout from the current directory, so you must pass an explicit path argument such as skills trust . from the repo root. Without it, doctor's project-skill count reads zero.

Why are my Hermes hook scripts not running?▼

Hooks silently fail when the scripts lack the executable bit, so doctor must check executability, not just presence. Also confirm hooks are registered in the profile config and that the first-session hook allowlist consent was accepted.