openhermes 2.6.1 → 4.0.0

package/harness/commands/refactor-clean.md

@@ -1,102 +0,0 @@
----
-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

@@ -1,78 +0,0 @@
----
-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

@@ -1,65 +0,0 @@
----
-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/security.md

@@ -1,93 +0,0 @@
----
-description: Run comprehensive security review
-agent: security-reviewer
-subtask: true
----
-
-# Security Review Command
-
-Conduct a comprehensive security review: $ARGUMENTS
-
-## Dependency audit
-
-!npm audit --json 2>&1 || echo '{"error":"npm audit unavailable"}'
-
-## Your Task
-
-Analyze the specified code for security vulnerabilities following OWASP guidelines and security best practices.
-
-## Security Checklist
-
-### OWASP Top 10
-
-1. **Injection** (SQL, NoSQL, OS command, LDAP)
-   - Check for parameterized queries
-   - Verify input sanitization
-   - Review dynamic query construction
-
-2. **Broken Authentication**
-   - Password storage (bcrypt, argon2)
-   - Session management
-   - Multi-factor authentication
-   - Password reset flows
-
-3. **Sensitive Data Exposure**
-   - Encryption at rest and in transit
-   - Proper key management
-   - PII handling
-
-4. **XML External Entities (XXE)**
-   - Disable DTD processing
-   - Input validation for XML
-
-5. **Broken Access Control**
-   - Authorization checks on every endpoint
-   - Role-based access control
-   - Resource ownership validation
-
-6. **Security Misconfiguration**
-   - Default credentials removed
-   - Error handling doesn't leak info
-   - Security headers configured
-
-7. **Cross-Site Scripting (XSS)**
-   - Output encoding
-   - Content Security Policy
-   - Input sanitization
-
-8. **Insecure Deserialization**
-   - Validate serialized data
-   - Implement integrity checks
-
-9. **Using Components with Known Vulnerabilities**
-   - Run `npm audit`
-   - Check for outdated dependencies
-
-10. **Insufficient Logging & Monitoring**
-    - Security events logged
-    - No sensitive data in logs
-    - Alerting configured
-
-### Additional Checks
-
-- [ ] Secrets in code (API keys, passwords)
-- [ ] Environment variable handling
-- [ ] CORS configuration
-- [ ] Rate limiting
-- [ ] CSRF protection
-- [ ] Secure cookie flags
-
-## Report Format
-
-### Critical Issues
-[Issues that must be fixed immediately]
-
-### High Priority
-[Issues that should be fixed before release]
-
-### Recommendations
-[Security improvements to consider]
-
----
-
-**IMPORTANT**: Security issues are blockers. Do not proceed until critical issues are resolved.

package/harness/commands/setup-pm.md

@@ -1,65 +0,0 @@
----
-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

@@ -1,99 +0,0 @@
----
-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.

package/harness/commands/test-coverage.md

@@ -1,80 +0,0 @@
----
-description: Analyze and improve test coverage
-agent: tdd-guide
-subtask: true
----
-
-# Test Coverage Command
-
-Analyze test coverage and identify gaps: $ARGUMENTS
-
-## Your Task
-
-1. **Run coverage report**: `npm test -- --coverage`
-2. **Analyze results** - Identify low coverage areas
-3. **Prioritize gaps** - Critical code first
-4. **Generate missing tests** - For uncovered code
-
-## Coverage Targets
-
-| Code Type | Target |
-|-----------|--------|
-| Standard code | 80% |
-| Financial logic | 100% |
-| Auth/security | 100% |
-| Utilities | 90% |
-| UI components | 70% |
-
-## Coverage Report Analysis
-
-### Summary
-```
-File           | % Stmts | % Branch | % Funcs | % Lines
----------------|---------|----------|---------|--------
-All files      |   XX    |    XX    |   XX    |   XX
-```
-
-### Low Coverage Files
-[Files below target, prioritized by criticality]
-
-### Uncovered Lines
-[Specific lines that need tests]
-
-## Test Generation
-
-For each uncovered area:
-
-### [Function/Component Name]
-
-**Location**: `src/path/file.ts:123`
-
-**Coverage Gap**: [description]
-
-**Suggested Tests**:
-```typescript
-describe('functionName', () => {
-  it('should [expected behavior]', () => {
-    // Test code
-  })
-
-  it('should handle [edge case]', () => {
-    // Edge case test
-  })
-})
-```
-
-## Coverage Improvement Plan
-
-1. **Critical** (add immediately)
-   - [ ] file1.ts - Auth logic
-   - [ ] file2.ts - Payment handling
-
-2. **High** (add this sprint)
-   - [ ] file3.ts - Core business logic
-
-3. **Medium** (add when touching file)
-   - [ ] file4.ts - Utilities
-
----
-
-**IMPORTANT**: Coverage is a metric, not a goal. Focus on meaningful tests, not just hitting numbers.

package/harness/commands/update-codemaps.md

@@ -1,81 +0,0 @@
----
-description: Update codemaps for codebase navigation
-agent: doc-updater
-subtask: true
----
-
-# Update Codemaps Command
-
-Update codemaps to reflect current codebase structure: $ARGUMENTS
-
-## Your Task
-
-Generate or update codemaps in `docs/CODEMAPS/` directory:
-
-1. **Analyze codebase structure**
-2. **Generate component maps**
-3. **Document relationships**
-4. **Update navigation guides**
-
-## Codemap Types
-
-### Architecture Map
-```
-docs/CODEMAPS/ARCHITECTURE.md
-```
-- High-level system overview
-- Component relationships
-- Data flow diagrams
-
-### Module Map
-```
-docs/CODEMAPS/MODULES.md
-```
-- Module descriptions
-- Public APIs
-- Dependencies
-
-### File Map
-```
-docs/CODEMAPS/FILES.md
-```
-- Directory structure
-- File purposes
-- Key files
-
-## Codemap Format
-
-### [Module Name]
-
-**Purpose**: [Brief description]
-
-**Location**: `src/[path]/`
-
-**Key Files**:
-- `file1.ts` - [purpose]
-- `file2.ts` - [purpose]
-
-**Dependencies**:
-- [Module A]
-- [Module B]
-
-**Exports**:
-- `functionName()` - [description]
-- `ClassName` - [description]
-
-**Usage Example**:
-```typescript
-import { functionName } from '@/module'
-```
-
-## Generation Process
-
-1. Scan directory structure
-2. Parse imports/exports
-3. Build dependency graph
-4. Generate markdown maps
-5. Validate links
-
----
-
-**TIP**: Keep codemaps updated when adding new modules or significant refactoring.