reflex-fuzz

Automate fuzz testing and iterative repair of reflection workflows with verification.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/rongarede/claude-skills-orchestration --skill reflex-fuzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflex-fuzz
Source: https://github.com/rongarede/claude-skills-orchestration/tree/main/skills/reflex-fuzz
Command: npx skills add https://github.com/rongarede/claude-skills-orchestration --skill reflex-fuzz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you proactively stress-test the reflection (reflex) workflow to surface failures, consistency drift, and control-breaker (CB) issues early—then iteratively fix and verify them.

Core Features & Use Cases

  • One-round full fuzz cycle: runs a strict multi-role loop (Explore → Decide → Implement → Audit → Commit → Journal → Memory) to keep changes controlled and reviewable.
  • Continuous fuzz mode with reporting: supports scheduled looping and progress reporting to track completed rounds and repair outcomes over time.
  • Data-driven diagnostics & guardrails: generates a prioritized problem list from trigger statistics and validates hook/config consistency before committing fixes.

Quick Start

Start a single fuzz round by asking for: /reflex-fuzz.

Frequently Asked Questions about reflex-fuzz

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

FAQPage Schema
How do I automate fuzz testing for a workflow orchestration system?

Automate workflow orchestration fuzzing by constructing test scenarios, diagnosing consistency drift, and applying guarded fixes with verification. The system runs a strict multi-role loop to keep changes controlled and reviewable.

What is the best way to continuously fuzz a reflection system to catch control-breaker issues?

Continuously fuzz a reflection system using scheduled looping with intervals and progress reporting. This surfaces failures and control-breaker issues early by tracking completed rounds and repair outcomes over time.

How do you validate hook and config consistency before committing workflow fixes?

Validate hook and config consistency by reading trigger statistics and SSOT transfer rules to generate a prioritized problem list. This data-driven diagnostic acts as a guardrail before fixes are committed.

Do I need python3 and jq installed to run automated code audit and fuzzing loops?

Yes, you need python3 and jq installed to run the automated code audit and fuzzing loops. These dependencies are required to process the trigger statistics and execute the incremental repair scripts.

Can I run a single fuzz testing round instead of continuous scheduled looping?

Yes, you can run a single-round full fuzz cycle instead of continuous scheduled looping. This executes a strict multi-role sequence from Explore to Memory to keep changes controlled and reviewable.

What are the limitations of using Git-backed iteration for workflow hook validation?

Git-backed iteration for hook validation requires enforcing a role-separated, incremental repair loop. Limitations include strict dependency on reading trigger statistics and SSOT transfer rules before applying guarded fixes.