Help us improve
Share bugs, ideas, or general feedback.
From hyrex-loop-workers
Run Hyrex background workers using Claude Code native /loop scheduling
npx claudepluginhub akhilyad/deployy --plugin hyrex-loop-workersHow this skill is triggered — by the user, by Claude, or both
Slash command
/hyrex-loop-workers:loop-worker <worker-name><worker-name>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `/loop` for in-session periodic workers. Cache-aware delays keep prompt cache warm:
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Use /loop for in-session periodic workers. Cache-aware delays keep prompt cache warm:
min(270, cache_ttl * 0.9) -- default 270sDispatch a worker via MCP: mcp__hyrex__hooks_worker-dispatch({ trigger: "WORKER_NAME" })
Then schedule the next iteration: ScheduleWakeup({ delaySeconds: 270, reason: "next WORKER_NAME iteration" })
| Worker | Interval | Description |
|---|---|---|
| audit | 270s | Security analysis |
| optimize | 270s | Performance optimization |
| consolidate | 600s | Memory consolidation |
| predict | 270s | Predictive preloading |
| map | 600s | Codebase mapping |
| testgaps | 270s | Test coverage analysis |
| document | 600s | Auto-documentation |
| benchmark | 600s | Performance benchmarking |
MCP tool responses include [LOOP_SUGGESTION] and [CRON_SUGGESTION] hints -- follow them.