hermit-patterns

Hermit Patterns Reference

This file contains detailed patterns, examples, and reference scripts for the Hermit role. It is meant to be consulted when needed, not loaded as primary instructions.

When to use this file:

• Looking for specific code smell examples
• Need detailed random file review workflow
• Implementing goal discovery scripts
• Checking command reference syntax
• Need worktree cleanup implementation

Primary instructions: See hermit.md for core role definition and workflow.

Cached forge reads: the issue/PR listing commands below use the one documented helper $GH_READ instead of a raw gh issue list / gh pr list. It routes label/state list queries through loom-daemon's ETag-cached REST path (forge … list --cached, #5056) — a validated 304 is free and never stale — and falls back to plain gh when the daemon is unreachable or the shape is not cacheable (freeform --search, no --json). Resolve it once per session:

GH_READ="gh"
_ghc="$(git rev-parse --show-toplevel 2>/dev/null)/.loom/scripts/gh-cached"
if [[ -x "$_ghc" ]] && "$_ghc" --version >/dev/null 2>&1; then GH_READ="$_ghc"; fi

Full policy: .loom/docs/gh-cached.md.

---

⚠️ --body @path Does NOT Expand — It Posts the Literal String

If you post a comment via gh issue comment / gh pr comment / gh api ... comments from a scratch file, --body @path (and gh api -f body=@path) posts the literal string @path, not the file's contents. Full pitfall, incident citation, and fixes: comment-body-literal-path.md.

---

Detailed Code Smell Examples

Look for these patterns that often indicate bloat:

1. Unnecessary Abstraction

// BAD: Over-abstracted
class DataFetcherFactory {
  createFetcher(): DataFetcher {
    return new ConcreteDataFetcher(new HttpClient());
  }
}

// GOOD: Direct and simple
async function fetchData(url: string): Promise<Data> {
  return fetch(url).then(r => r.json());
}