scbe-dry-run-rubix

Verify cross-language SCBE changes and emit SHIP, HOLD, or BLOCK verdicts.

6|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-dry-run-rubix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scbe-dry-run-rubix
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/plugins/scbe-verify/skills/scbe-dry-run-rubix
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-dry-run-rubix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dry-run cross-language verification for SCBE changes to detect regressions across languages, invariants, and runtime surfaces before merging.

Core Features & Use Cases

  • Dry-run style verification across affected languages (TypeScript, Python, Rust) prior to live execution.
  • Parity checks across touched surfaces, including Windows path handling, subprocess dispatch, and encoding normalization.
  • Gate-style verdict emission (SHIP, HOLD, or BLOCK) with actionable remediation notes for quick triage.

Quick Start

Trigger the dry-run rubix verification on the current change set to obtain a concise ship, hold, or block verdict.

Frequently Asked Questions about scbe-dry-run-rubix

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

FAQPage Schema
How do I check cross-language parity before merging TypeScript, Python, and Rust changes?

Cross-language parity verification applies a dry-run rubix to touched language surfaces, detecting regressions across TypeScript, Python, and Rust before live execution. It outputs a deterministic SHIP, HOLD, or BLOCK verdict with concrete remediation guidance.

What is dry-run verification for cross-language changes?

Dry-run verification is a pre-merge process that identifies cross-language changes affecting SCBE components and invariants. It checks touched language surfaces to detect parity gaps, Windows path issues, subprocess dispatch anomalies, and normalization edge cases.

How do I detect Windows path issues and subprocess dispatch anomalies in my codebase?

Detect Windows path issues and subprocess dispatch anomalies by triggering dry-run rubix verification on your current change set. It evaluates affected language surfaces and emits actionable remediation notes aligned to the repository's 14-layer math surface.

Does cross-language pre-merge verification require any external dependencies?

Cross-language pre-merge verification requires no external dependencies. It operates directly on your current change set to summarize touched surfaces and output a deterministic verdict.

What is the best way to gate merges for encoding normalization edge cases across multiple languages?

Gate merges for encoding normalization edge cases by applying dry-run rubix verification across affected TypeScript, Python, and Rust surfaces. It emits a deterministic SHIP, HOLD, or BLOCK verdict with actionable triage notes.