jamesaphoenix/tx - Page 2

tx-workers-runtime

Operate workers, daemons, coordinators, cycle scans, and hook installation paths. Use when working in Codex and the user needs tx commands from this area.

verify-invariants

Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.

release

Release a new lockstep version of tx to GitHub and npm with preflight validation, workflow monitoring, and registry verification.

release

Cut a lockstep tx release with enforced preflight validation, workflow monitoring, and npm verification. Use when bumping versions, tagging releases, repairing partial publishes, or checking publish readiness.

docs-diagrams

Add or refine diagrams in documentation, especially Mermaid workflow diagrams in apps/docs. Use when a docs page explains actor handoffs, phase gates, failure paths, state transitions, or multi-step flows that are clearer as a diagram.

docs-diagrams

Add or refine diagrams in documentation, especially Mermaid workflow diagrams in apps/docs. Use when a docs page explains actor handoffs, phase gates, failure paths, state transitions, or multi-step flows that are clearer as a diagram.

tx-cycle

Run a tx cycle scan — sub-agent swarm for automated codebase issue discovery. Use when the user mentions "cycle", "scan", or "find issues".

cycle

Run a tx cycle scan — sub-agent swarm for codebase issue discovery. Use when the user explicitly mentions "cycle". Do NOT use Claude Code teams (TeamCreate/SendMessage) for this — use tx cycle CLI instead.

test-diagnostics

Profile all test files to find slow, hanging, or failing tests. Use when tests seem slow or when vitest hangs.

test-quiet

Run tests with context-efficient output. Hides passing test output, shows ONLY failures. Use when running tests, checking if tests pass, or verifying changes. Also detects flaky tests.

debug-hooks

Debug Claude Code hook artifacts. Use when investigating why ralph failed, what hooks fired, what was blocked, or reviewing hook behavior for a run.