openhermes 1.5.2 → 1.12.1

package/harness/commands/loop-start.md

@@ -0,0 +1,38 @@
+---
+description: Start a managed autonomous loop pattern with safety defaults
+agent: loop-operator
+subtask: true
+---
+
+# Loop Start Command
+
+Start a managed autonomous loop pattern with safety defaults.
+
+## Usage
+
+`/loop-start [pattern] [--mode safe|fast]`
+
+- `pattern`: `sequential`, `continuous-pr`, `rfc-dag`, `infinite`
+- `--mode`:
+  - `safe` (default): strict quality gates and checkpoints
+  - `fast`: reduced gates for speed
+
+## Flow
+
+1. Confirm repository state and branch strategy.
+2. Select loop pattern and model tier strategy.
+3. Enable required hooks/profile for the chosen mode.
+4. Create loop plan and write runbook under `.opencode/plans/`.
+5. Print commands to start and monitor the loop.
+
+## Required Safety Checks
+
+- Verify tests pass before first loop iteration.
+- Ensure `OH_HOOK_PROFILE` is not disabled globally.
+- Ensure loop has explicit stop condition.
+
+## Arguments
+
+$ARGUMENTS:
+- `<pattern>` optional (`sequential|continuous-pr|rfc-dag|infinite`)
+- `--mode safe|fast` optional

package/harness/commands/loop-status.md

@@ -0,0 +1,30 @@
+---
+description: Inspect active loop state, progress, and failure signals
+agent: OpenHermes
+subtask: true
+---
+
+# Loop Status Command
+
+Inspect active loop state, progress, and failure signals.
+
+## Usage
+
+`/loop-status [--watch]`
+
+## What to Report
+
+- active loop pattern
+- current phase and last successful checkpoint
+- failing checks (if any)
+- estimated time/cost drift
+- recommended intervention (continue/pause/stop)
+
+## Watch Mode
+
+When `--watch` is present, refresh status periodically and surface state changes.
+
+## Arguments
+
+$ARGUMENTS:
+- `--watch` optional

package/harness/commands/memory-search.md

@@ -10,7 +10,7 @@ Search openhermes memory for: $ARGUMENTS
 
 ## Your Task
 
-1. Call `hm_search` with query="$ARGUMENTS" to get raw results
+1. Call `search_memory` with query="$ARGUMENTS" to get raw results
 2. Summarize the top 5 results with natural language interpretation
 3. Highlight patterns, recurring themes, and actionable insights
 4. Return a structured report
@@ -34,4 +34,4 @@ Search openhermes memory for: $ARGUMENTS
 
 ### Recommended Next Query
 
-[Suggest a follow-up hm_search query for deeper exploration]
+[Suggest a follow-up search_memory query for deeper exploration]

package/harness/commands/model-route.md

@@ -0,0 +1,32 @@
+---
+description: Recommend optimal model tier for the current task
+agent: OpenHermes
+subtask: true
+---
+
+# Model Route Command
+
+Recommend the best model tier for the current task by complexity and budget.
+
+## Usage
+
+`/model-route [task-description] [--budget low|med|high]`
+
+## Routing Heuristic
+
+- `haiku`: deterministic, low-risk mechanical changes
+- `sonnet`: default for implementation and refactors
+- `opus`: architecture, deep review, ambiguous requirements
+
+## Required Output
+
+- recommended model
+- confidence level
+- why this model fits
+- fallback model if first attempt fails
+
+## Arguments
+
+$ARGUMENTS:
+- `[task-description]` optional free-text
+- `--budget low|med|high` optional

package/harness/commands/orchestrate.md

@@ -0,0 +1,88 @@
+---
+description: Orchestrate multiple agents for complex tasks
+agent: planner
+subtask: true
+---
+
+# Orchestrate Command
+
+Orchestrate multiple specialized agents for this complex task: $ARGUMENTS
+
+## Your Task
+
+1. **Analyze task complexity** and break into subtasks
+2. **Identify optimal agents** for each subtask
+3. **Create execution plan** with dependencies
+4. **Coordinate execution** - parallel where possible
+5. **Synthesize results** into unified output
+
+## Available Agents
+
+| Agent | Specialty | Use For |
+|-------|-----------|---------|
+| planner | Implementation planning | Complex feature design |
+| architect | System design | Architectural decisions |
+| code-reviewer | Code quality | Review changes |
+| security-reviewer | Security analysis | Vulnerability detection |
+| tdd-guide | Test-driven dev | Feature implementation |
+| build-error-resolver | Build fixes | TypeScript/build errors |
+| e2e-runner | E2E testing | User flow testing |
+| doc-updater | Documentation | Updating docs |
+| refactor-cleaner | Code cleanup | Dead code removal |
+| review-go | Go code | Go-specific review |
+| build-go | Go builds | Go build errors |
+| review-database | Database | Query optimization |
+
+## Orchestration Patterns
+
+### Sequential Execution
+```
+planner → tdd-guide → code-reviewer → security-reviewer
+```
+Use when: Later tasks depend on earlier results
+
+### Parallel Execution
+```
+┌→ security-reviewer
+planner →├→ code-reviewer
+└→ architect
+```
+Use when: Tasks are independent
+
+### Fan-Out/Fan-In
+```
+         ┌→ agent-1 ─┐
+planner →├→ agent-2 ─┼→ synthesizer
+         └→ agent-3 ─┘
+```
+Use when: Multiple perspectives needed
+
+## Execution Plan Format
+
+### Phase 1: [Name]
+- Agent: [agent-name]
+- Task: [specific task]
+- Depends on: [none or previous phase]
+
+### Phase 2: [Name] (parallel)
+- Agent A: [agent-name]
+  - Task: [specific task]
+- Agent B: [agent-name]
+  - Task: [specific task]
+- Depends on: Phase 1
+
+### Phase 3: Synthesis
+- Combine results from Phase 2
+- Generate unified output
+
+## Coordination Rules
+
+1. **Plan before execute** - Create full execution plan first
+2. **Minimize handoffs** - Reduce context switching
+3. **Parallelize when possible** - Independent tasks in parallel
+4. **Clear boundaries** - Each agent has specific scope
+5. **Single source of truth** - One agent owns each artifact
+
+---
+
+**NOTE**: Complex tasks benefit from multi-agent orchestration. Simple tasks should use single agents directly.

package/harness/commands/quality-gate.md

@@ -0,0 +1,35 @@
+---
+description: Run quality pipeline on demand for a file or project scope
+agent: OpenHermes
+subtask: true
+---
+
+# Quality Gate Command
+
+Run the quality pipeline on demand for a file or project scope.
+
+## Usage
+
+`/quality-gate [path|.] [--fix] [--strict]`
+
+- default target: current directory (`.`)
+- `--fix`: allow auto-format/fix where configured
+- `--strict`: fail on warnings where supported
+
+## Pipeline
+
+1. Detect language/tooling for target.
+2. Run formatter checks.
+3. Run lint/type checks when available.
+4. Produce a concise remediation list.
+
+## Notes
+
+This command mirrors hook behavior but is operator-invoked.
+
+## Arguments
+
+$ARGUMENTS:
+- `[path|.]` optional target path
+- `--fix` optional
+- `--strict` optional

package/harness/commands/refactor-clean.md

@@ -0,0 +1,102 @@
+---
+description: Remove dead code and consolidate duplicates
+agent: refactor-cleaner
+subtask: true
+---
+
+# Refactor Clean Command
+
+Analyze and clean up the codebase: $ARGUMENTS
+
+## Your Task
+
+1. **Detect dead code** using analysis tools
+2. **Identify duplicates** and consolidation opportunities
+3. **Safely remove** unused code with documentation
+4. **Verify** no functionality broken
+
+## Detection Phase
+
+### Run Analysis Tools
+
+```bash
+# Find unused exports
+npx knip
+
+# Find unused dependencies
+npx depcheck
+
+# Find unused TypeScript exports
+npx ts-prune
+```
+
+### Manual Checks
+
+- Unused functions (no callers)
+- Unused variables
+- Unused imports
+- Commented-out code
+- Unreachable code
+- Unused CSS classes
+
+## Removal Phase
+
+### Before Removing
+
+1. **Search for usage** - grep, find references
+2. **Check exports** - might be used externally
+3. **Verify tests** - no test depends on it
+4. **Document removal** - git commit message
+
+### Safe Removal Order
+
+1. Remove unused imports first
+2. Remove unused private functions
+3. Remove unused exported functions
+4. Remove unused types/interfaces
+5. Remove unused files
+
+## Consolidation Phase
+
+### Identify Duplicates
+
+- Similar functions with minor differences
+- Copy-pasted code blocks
+- Repeated patterns
+
+### Consolidation Strategies
+
+1. **Extract utility function** - for repeated logic
+2. **Create base class** - for similar classes
+3. **Use higher-order functions** - for repeated patterns
+4. **Create shared constants** - for magic values
+
+## Verification
+
+After cleanup:
+
+1. `npm run build` - builds successfully
+2. `npm test` - all tests pass
+3. `npm run lint` - no new lint errors
+4. Manual smoke test - features work
+
+## Report Format
+
+```
+Dead Code Analysis
+==================
+
+Removed:
+- file.ts: functionName (unused export)
+- utils.ts: helperFunction (no callers)
+
+Consolidated:
+- formatDate() and formatDateTime() → dateUtils.format()
+
+Remaining (manual review needed):
+- oldComponent.tsx: potentially unused, verify with team
+```
+
+---
+
+**CAUTION**: Always verify before removing. When in doubt, ask or add `// TODO: verify usage` comment.

package/harness/commands/rust-build.md

@@ -0,0 +1,78 @@
+---
+description: Fix Rust build errors and borrow checker issues
+agent: build-rust
+subtask: true
+---
+
+# Rust Build Command
+
+Fix Rust build, clippy, and dependency errors: $ARGUMENTS
+
+## Your Task
+
+1. **Run cargo check**: `cargo check 2>&1`
+2. **Run cargo clippy**: `cargo clippy -- -D warnings 2>&1`
+3. **Fix errors** one at a time
+4. **Verify fixes** don't introduce new errors
+
+## Common Rust Errors
+
+### Borrow Checker
+```
+cannot borrow `x` as mutable because it is also borrowed as immutable
+```
+**Fix**: Restructure to end immutable borrow first; clone only if justified
+
+### Type Mismatch
+```
+mismatched types: expected `T`, found `U`
+```
+**Fix**: Add `.into()`, `as`, or explicit type conversion
+
+### Missing Import
+```
+unresolved import `crate::module`
+```
+**Fix**: Fix the `use` path or declare the module (add Cargo.toml deps only for external crates)
+
+### Lifetime Errors
+```
+does not live long enough
+```
+**Fix**: Use owned type or add lifetime annotation
+
+### Trait Not Implemented
+```
+the trait `X` is not implemented for `Y`
+```
+**Fix**: Add `#[derive(Trait)]` or implement manually
+
+## Fix Order
+
+1. **Build errors** - Code must compile
+2. **Clippy warnings** - Fix suspicious constructs
+3. **Formatting** - `cargo fmt` compliance
+
+## Build Commands
+
+```bash
+cargo check 2>&1
+cargo clippy -- -D warnings 2>&1
+cargo fmt --check 2>&1
+cargo tree --duplicates
+cargo test
+```
+
+## Verification
+
+After fixes:
+```bash
+cargo check                  # Should succeed
+cargo clippy -- -D warnings  # No warnings allowed
+cargo fmt --check            # Formatting should pass
+cargo test                   # Tests should pass
+```
+
+---
+
+**IMPORTANT**: Fix errors only. No refactoring, no improvements. Get the build green with minimal changes.

package/harness/commands/rust-review.md

@@ -0,0 +1,65 @@
+---
+description: Rust code review for ownership, safety, and idiomatic patterns
+agent: review-rust
+subtask: true
+---
+
+# Rust Review Command
+
+Review Rust code for idiomatic patterns and best practices: $ARGUMENTS
+
+## Your Task
+
+1. **Analyze Rust code** for idioms and patterns
+2. **Check ownership** - borrowing, lifetimes, unnecessary clones
+3. **Review error handling** - proper `?` propagation, no unwrap in production
+4. **Verify safety** - unsafe usage, injection, secrets
+
+## Review Checklist
+
+### Safety (CRITICAL)
+- [ ] No unchecked `unwrap()`/`expect()` in production paths
+- [ ] `unsafe` blocks have `// SAFETY:` comments
+- [ ] No SQL/command injection
+- [ ] No hardcoded secrets
+
+### Ownership (HIGH)
+- [ ] No unnecessary `.clone()` to satisfy borrow checker
+- [ ] `&str` preferred over `String` in function parameters
+- [ ] `&[T]` preferred over `Vec<T>` in function parameters
+- [ ] No excessive lifetime annotations where elision works
+
+### Error Handling (HIGH)
+- [ ] Errors propagated with `?`; use `.context()` in `anyhow`/`eyre` application code
+- [ ] No silenced errors (`let _ = result;`)
+- [ ] `thiserror` for library errors, `anyhow` for applications
+
+### Concurrency (HIGH)
+- [ ] No blocking in async context
+- [ ] Bounded channels preferred
+- [ ] `Mutex` poisoning handled
+- [ ] `Send`/`Sync` bounds correct
+
+### Code Quality (MEDIUM)
+- [ ] Functions under 50 lines
+- [ ] No deep nesting (>4 levels)
+- [ ] Exhaustive matching on business enums
+- [ ] Clippy warnings addressed
+
+## Report Format
+
+### CRITICAL Issues
+- [file:line] Issue description
+  Suggestion: How to fix
+
+### HIGH Issues
+- [file:line] Issue description
+  Suggestion: How to fix
+
+### MEDIUM Issues
+- [file:line] Issue description
+  Suggestion: How to fix
+
+---
+
+**TIP**: Run `cargo clippy -- -D warnings` and `cargo fmt --check` for automated checks.

package/harness/commands/setup-pm.md

@@ -0,0 +1,65 @@
+---
+description: Configure package manager preference for OpenHermes
+agent: OpenHermes
+subtask: true
+---
+
+# Setup Package Manager Command
+
+Configure your preferred package manager: $ARGUMENTS
+
+## Your Task
+
+Set up package manager preference for the project or globally.
+
+## Detection Order
+
+1. **Environment variable**: `OPENHERMES_PACKAGE_MANAGER`
+2. **Project config**: `.opencode/package-manager.json`
+3. **package.json**: `packageManager` field
+4. **Lock file**: Auto-detect from lock files
+5. **Global config**: `~/.config/opencode/package-manager.json`
+6. **Fallback**: First available
+
+## Configuration Options
+
+### Option 1: Environment Variable
+```bash
+$env:OPENHERMES_PACKAGE_MANAGER="pnpm"
+```
+
+### Option 2: Project Config
+```bash
+# Create .opencode/package-manager.json
+echo '{"packageManager": "pnpm"}' | Out-File -Encoding utf8 .opencode/package-manager.json
+```
+
+### Option 3: package.json
+```json
+{
+  "packageManager": "pnpm@8.0.0"
+}
+```
+
+### Option 4: Global Config
+```bash
+# Create ~/.config/opencode/package-manager.json
+echo '{"packageManager": "yarn"}' | Out-File -Encoding utf8 ~/.config/opencode/package-manager.json
+```
+
+## Supported Package Managers
+
+| Manager | Lock File | Commands |
+|---------|-----------|----------|
+| npm | package-lock.json | `npm install`, `npm run` |
+| pnpm | pnpm-lock.yaml | `pnpm install`, `pnpm run` |
+| yarn | yarn.lock | `yarn install`, `yarn run` |
+| bun | bun.lockb | `bun install`, `bun run` |
+
+## Verification
+
+Check current setting by inspecting detection order from top down.
+
+---
+
+**TIP**: For consistency across team, add `packageManager` field to package.json.

package/harness/commands/skill-create.md

@@ -0,0 +1,99 @@
+---
+description: Generate SKILL.md files from git history analysis
+agent: OpenHermes
+subtask: true
+---
+
+# Skill Create Command
+
+Analyze git history to generate OpenHermes skills: $ARGUMENTS
+
+## Your Task
+
+1. **Analyze commits** - Pattern recognition from history
+2. **Extract patterns** - Common practices and conventions
+3. **Generate SKILL.md** - Structured skill documentation in OH harness format
+
+## Analysis Process
+
+### Step 1: Gather Commit Data
+```bash
+# Recent commits
+git log --oneline -100
+
+# Commits by file type
+git log --name-only --pretty=format: | sort | uniq -c | sort -rn
+
+# Most changed files
+git log --pretty=format: --name-only | sort | uniq -c | sort -rn | head -20
+```
+
+### Step 2: Identify Patterns
+
+**Commit Message Patterns**:
+- Common prefixes (feat, fix, refactor)
+- Naming conventions
+- Co-author patterns
+
+**Code Patterns**:
+- File structure conventions
+- Import organization
+- Error handling approaches
+
+**Review Patterns**:
+- Common review feedback
+- Recurring fix types
+- Quality gates
+
+### Step 3: Generate SKILL.md
+
+```markdown
+# [Skill Name]
+
+## Overview
+[What this skill teaches]
+
+## Patterns
+
+### Pattern 1: [Name]
+- When to use
+- Implementation
+- Example
+
+### Pattern 2: [Name]
+- When to use
+- Implementation
+- Example
+
+## Best Practices
+
+1. [Practice 1]
+2. [Practice 2]
+3. [Practice 3]
+
+## Common Mistakes
+
+1. [Mistake 1] - How to avoid
+2. [Mistake 2] - How to avoid
+
+## Examples
+
+### Good Example
+```[language]
+// Code example
+```
+
+### Anti-pattern
+```[language]
+// What not to do
+```
+```
+
+## Output
+
+Creates:
+- `skills/[name]/SKILL.md` - Skill documentation in OpenHermes harness format
+
+---
+
+**TIP**: Run `/skill-create` after several related commits to extract reusable patterns.