From oh-my-harness
Checks status of oh-my-harness agent processes: tmux pane liveness, git branch progress (commits, files changed), and suggests next actions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/oh-my-harness:agent-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check the status of running oh-my-harness agents.
Check the status of running oh-my-harness agents.
Usage: /agent-status
Read agent state from .claude/.omh/agents.json. If no file exists, report "No active agents." and exit.
Read useWorktree from agents.json to determine how to check progress.
Check tmux session: tmux has-session -t "{tmuxSession}" 2>/dev/null
If the session doesn't exist, report that agents are no longer running and suggest cleanup.
For each agent, check:
tmux list-panes -t "{tmuxSession}" -F '#{pane_index} #{pane_pid} #{pane_dead}'useWorktree is true:
git log "main..omh/agent-{i}" --onelinegit diff "main...omh/agent-{i}" --statuseWorktree is false:
Display status table:
| Agent | Branch | Status | Commits | Files Changed |
|-------|-----------------|---------|---------|---------------|
| 1 | omh/agent-1 | running | 3 | 5 |
| 2 | omh/agent-2 | done | 1 | 2 |
When useWorktree is false, omit Branch/Commits/Files columns and show only Agent/Status.
Suggest next actions based on status:
/agent-apply (worktree mode) or /agent-stop/agent-stop {id} for specific onesProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub hoya324/oh-my-harness --plugin oh-my-harness