logix-cli

Automate Logix verification and live runtime inspection via CLI.

4|1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/yoyooyooo/logix --skill logix-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logix-cli
Source: https://github.com/yoyooyooo/logix/tree/main/skills/logix-cli
Command: npx skills add https://github.com/yoyooyooo/logix --skill logix-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you validate Logix Programs and gather machine-readable evidence from shell or CI, while also inspecting a live Logix runtime to support evidence-driven repair workflows.

Core Features & Use Cases

  • Verification lane (check/trial/compare): Produces structured verification artifacts (VerificationControlPlaneReport) for code changes and before/after closure.
  • Live lane (live tasks): Queries an active runtime for status, targets, state, actions, events, timelines, and canonical evidence exports for later verification.
  • Agent First CLI loop support: Provides strict command/entry rules, schema mirror usage, artifact selection guidance, and guardrails to prevent mixing live output with verification verdicts.

Quick Start

Ask the Agent to run a Logix trial for your Program entry and return the primary verification report artifact from outRoot.

Frequently Asked Questions about logix-cli

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

FAQPage Schema
How do I automate Logix verification for frontend state workflows in CI?

Automate Logix verification by invoking the Logix CLI from your shell with a stable runId and outRoot. It runs Program entry checks and trial startup verification, generating a structured VerificationControlPlaneReport for your CI pipeline.

What is live runtime inspection for Logix Programs?

Live runtime inspection queries an active Logix runtime to capture status, state, actions, events, and timelines. It exports canonical evidence from the running environment to support evidence-driven repair workflows without mixing outputs with verification verdicts.

How do I capture live debugging evidence from a running React runtime?

Capture live debugging evidence by running live tasks through the Logix CLI against your active runtime. This queries targets and events, exporting canonical evidence artifacts for later verification while preventing the mixing of live outputs with verification verdicts.

Can I perform before and after comparison checks for Logix Programs from the shell?

Yes, you can perform before and after compare closure from the shell using the Logix CLI. It validates code changes by producing structured verification artifacts that compare initial and updated Program states.

Do I need a stable runId and outRoot to run Logix CLI checks?

Yes, invoking Logix CLI requires stable runId and outRoot parameters to execute verification and live tasks successfully. You must also reference the command grammar in commands.v1.json to ensure strict entry rule compliance.

Why should I avoid mixing live debugging outputs with verification verdicts?

Avoid mixing live debugging outputs with verification verdicts to maintain the integrity of structured primary reports. The Skill enforces strict guardrails and artifact selection guidance to separate live runtime evidence from VerificationControlPlaneReport artifacts.