Read JSON state files to report active OMG execution modes and progress.
npx skills add https://github.com/HyperionBurn/searchv1beta --skill status-hyperionburn
Please help me install this Agent Skill. Skill: status Source: https://github.com/HyperionBurn/searchv1beta/tree/main/.github/skills/status Command: npx skills add https://github.com/HyperionBurn/searchv1beta --skill status-hyperionburn
You need a reliable way to understand what the system is currently running and how far each active workflow has progressed, especially after starting, canceling, or resuming execution.
Use the status skill to display the current state of all active OMG modes and their progress.
High-intent search queries and answers about installing and using this skill.
To check async pipeline progress, it reads JSON state files from the .omg/state directory and renders a human-readable report showing phases, iterations, task completion counts, and worker activity for active modes.
For post-interruption verification, it reads JSON state files to display current phases, last failure summaries, and files modified so far across modes like omg-autopilot, ralph, and ultraqa.
Yes, you can view detailed JSON state and git activity by enabling optional verbose diagnostics, which also provides a directory listing for deeper troubleshooting of active execution modes.
Yes, status reporting supports self-improve and team modes, reading JSON state files to track cycles, stages, and task completion counts for each running mode.
Active modes may not show updated task completion counts if the JSON state files in the .omg/state directory are not being written or refreshed by the async pipeline workers.
cheafiReport active OMG modes and progress from local state files.
Chachamaru127Diagnose CI/CD pipeline failures and propose remediation fixes.
jmstar85Read OMG state files and summarize active agents and workflow progress.
oakossInspect TanStack Query, Router, and Form state in React applications.
