Coding Workflow — Hermes & Claude Code
Shared workflow rules for coding tasks. Both agents read this skill; rules are agent-agnostic (terminal/git/gh only).
1. Division of labor
| Task |
Agent |
| Home Assistant, Hermes gateway/admin, scheduling (cron), memory, audits, container/system ops |
Hermes |
| In-repo code changes, features, bugfixes, PRs (in any repo the user works on) |
Claude Code (Hermes delegates via claude -p or interactive) |
| Repo docs (docs/, README, skills) |
Either — follow repo-conventions |
Hermes orchestrates and can delegate coding to Claude Code. Claude Code works inside a repo; it does NOT manage the Hermes agent, HA gateway, or cron.
2. Plan first (MANDATORY)
Never jump straight into editing. For anything non-trivial:
- Restate the goal and constraints in your own words.
- Read the repo's AGENTS.md/CLAUDE.md and
.claude/skills/; explore the relevant files.
- Write the plan (files to touch, approach, test strategy) and get explicit user approval before mutating.
- If the user says "grill me" / "stress-test this" — interview them about the plan branch by branch until the design tree is resolved.
3. Confirm before mutating (MANDATORY)
- Per-action approval for: system changes,
git push, opening PRs, anything destructive.
- A prior "yes" is not standing approval — re-confirm scope.
- Prefer approval-free git ops: regular push, new commit, merge over rebase; no force-push without explicit approval.
4. Review
- Run the repo's own checks before any PR: its
make test/make pre-commit where defined, or the CI-equivalent.
- Verify git identity before committing (wrong email = phantom PR participants — see repo-conventions).
- Review your own diff before pushing; for PRs, diff against the base branch.
5. Per-repo PR flows
Load repo-conventions and follow the row for that repo. Default when unsure: branch from the default branch, conventional commit, squash-merge PR with a conventional title.
6. Skills & plugins maintenance
- 2-track governance (encoded in the shared AGENTS.md): Track 1 = curated skills, versioned in the chezmoi source, deployed via
skill-deployment; Track 2 = third-party suites as Claude Code plugins (e.g. superpowers). Never hand-copy a Track-2 suite into Track 1 — it fights its own updater.
- Chat-made decisions get encoded into the governing skill (this one,
repo-conventions, or the repo's own skill) — never left only in memory.
1---2name: coding-workflow3description: Use when starting any coding work across the repos. Division of labor between Hermes and Claude Code, plan-first workflow, confirm-before-mutate, review, and per-repo PR flows (see repo-conventions).4---56# Coding Workflow — Hermes & Claude Code78Shared workflow rules for coding tasks. Both agents read this skill; rules are agent-agnostic (terminal/git/gh only).910## 1. Division of labor1112| Task | Agent |13|---|---|14| Home Assistant, Hermes gateway/admin, scheduling (cron), memory, audits, container/system ops | **Hermes** |15| In-repo code changes, features, bugfixes, PRs (in any repo the user works on) | **Claude Code** (Hermes delegates via `claude -p` or interactive) |16| Repo docs (docs/, README, skills) | Either — follow repo-conventions |1718Hermes orchestrates and can delegate coding to Claude Code. Claude Code works inside a repo; it does NOT manage the Hermes agent, HA gateway, or cron.1920## 2. Plan first (MANDATORY)2122Never jump straight into editing. For anything non-trivial:231. Restate the goal and constraints in your own words.242. Read the repo's AGENTS.md/CLAUDE.md and `.claude/skills/`; explore the relevant files.253. Write the plan (files to touch, approach, test strategy) and get explicit user approval before mutating.264. If the user says "grill me" / "stress-test this" — interview them about the plan branch by branch until the design tree is resolved.2728## 3. Confirm before mutating (MANDATORY)2930- Per-action approval for: system changes, `git push`, opening PRs, anything destructive.31- A prior "yes" is not standing approval — re-confirm scope.32- Prefer approval-free git ops: regular push, new commit, merge over rebase; no force-push without explicit approval.3334## 4. Review3536- Run the repo's own checks before any PR: its `make test`/`make pre-commit` where defined, or the CI-equivalent.37- Verify git identity before committing (wrong email = phantom PR participants — see repo-conventions).38- Review your own diff before pushing; for PRs, diff against the base branch.3940## 5. Per-repo PR flows4142Load `repo-conventions` and follow the row for that repo. Default when unsure: branch from the default branch, conventional commit, squash-merge PR with a conventional title.4344## 6. Skills & plugins maintenance4546- **2-track governance** (encoded in the shared AGENTS.md): Track 1 = curated skills, versioned in the chezmoi source, deployed via `skill-deployment`; Track 2 = third-party suites as Claude Code plugins (e.g. superpowers). Never hand-copy a Track-2 suite into Track 1 — it fights its own updater.47- Chat-made decisions get encoded into the governing skill (this one, `repo-conventions`, or the repo's own skill) — never left only in memory.
aminedjeghri