cycle-verify

Automate the opsx verify cycle across verify, triage, apply+test, and explore phases via tmux sessions.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill cycle-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cycle-verify
Source: https://github.com/dentedgem9846-claw/chronocrystal-opsx/tree/main/.pi/skills/cycle-verify
Command: npx skills add https://github.com/dentedgem9846-claw/chronocrystal-opsx --skill cycle-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the opsx verify cycle for a change to ensure validated releases before archiving.

Core Features & Use Cases

  • End-to-end cycle orchestration covering verify, triage, apply+test, and explore phases.
  • Enforces clean working trees, bounded commits, and artifact cleanup between runs.
  • Use Case: After implementing a change, run the cycle to verify that all checks pass before archiving.

Quick Start

Run the cycle for a change by executing the run-cycle script for the chosen change-name from the project root.

Frequently Asked Questions about cycle-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the opsx verification cycle for a git change?

To automate the opsx verification cycle, execute the run-cycle script from the project root with your chosen change-name. This orchestrates the full verify, triage, apply+test, and explore phases end-to-end via a tmux session.

What does the opsx verify cycle include before archiving a change?

The opsx verify cycle includes four phases: verify, triage, apply+test, and explore. It ensures validated releases by orchestrating the full cycle and coordinating phase transitions before archiving.

Do I need a clean working tree to run the verification cycle?

Yes, the verification cycle enforces a clean working tree before execution. It also requires running from the project root and cleans prior artifacts between runs to maintain validation integrity.

How does tmux coordinate the opsx verify cycle phases?

Tmux coordinates the opsx verify cycle phase transitions by managing the session while invoking the run-cycle script. This ensures the verify, triage, apply+test, and explore phases execute sequentially.

When should I run the opsx verify cycle in my workflow?

You should run the opsx verify cycle after implementation is complete and before archiving. It validates that all checks pass for your change, ensuring the release is safe to archive.