runtime-validation-repair-worker

Repair validator regressions across CLI, API, and browser surfaces.

51|6|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Qredence/fleet-rlm --skill runtime-validation-repair-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-validation-repair-worker
Source: https://github.com/Qredence/fleet-rlm/tree/main/.factory/skills/runtime-validation-repair-worker
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill runtime-validation-repair-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repair regressions caused by validation during the fleet_rlm simplification mission.

Core Features & Use Cases

  • Reproduce failing validators and apply focused repairs to regenerate stable runtime behavior
  • Enforce a structured repair workflow anchored to mission-worker-base, with regression handoffs, targeted fixes, and revalidation
  • Provide a clean handoff including pre/post-repair evidence, validation results, and test updates

Quick Start

Start a repair session by initiating the runtime-validation-repair workflow for the current session.

Frequently Asked Questions about runtime-validation-repair-worker

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

FAQPage Schema
How do I repair runtime validation regressions across CLI, API, and browser surfaces?

Runtime validation regressions are repaired by reproducing failing validators and applying targeted fixes to restore stable behavior with minimal changes across CLI, API, and browser surfaces. The workflow enforces structured regression handoffs and revalidation.

What is the best way to fix validator failures discovered during a simplification mission?

Fixing validator failures during a simplification mission requires a disciplined repair workflow that reproduces the failing validator, applies focused repairs, and runs format, lint, and type checks as part of verification to ensure stable runtime behavior.

Do I need to run initialization steps before starting a validation repair workflow?

Yes, validation repair requires prior execution of mission-worker-base initialization steps before starting the workflow. This prerequisite ensures the environment is properly configured for regression handoffs and targeted fixes.

How does a structured repair workflow handle regression handoffs and revalidation?

A structured repair workflow handles regression handoffs by reproducing failing validators, applying focused repairs, and enforcing revalidation through format, lint, and type checks. It provides a clean handoff including pre/post-repair evidence and validation results.

Can I apply minimal changes to fix runtime validation regressions without breaking existing tests?

Applying minimal changes to fix runtime validation regressions requires running format, lint, and type checks as part of verification. The workflow enforces targeted fixes and revalidation to ensure existing behavior remains stable without breaking tests.

What evidence do I get after completing a runtime validation regression repair?

After completing a runtime validation regression repair, you receive a clean handoff including pre/post-repair evidence, validation results, and test updates. This documentation ensures the targeted fixes are transparent and verifiable.