skills.rest
fireflyframework
fireflyframeworkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

debugging-reactive-chains

Diagnose reactive chain errors in Firefly Framework services using Reactor debugging techniques.

Updated Aug 27, 2026
Search Tags:#debugging#context#logs#checkpoint#reactive#reactor#sagas
One-click install
npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill debugging-reactive-chains
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-reactive-chains
Source: https://github.com/fireflyframework/fireflyframework-claude-skills/tree/main/skills/debugging-reactive-chains
Command: npx skills add https://github.com/fireflyframework/fireflyframework-claude-skills --skill debugging-reactive-chains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging reactive chains in Firefly Framework services can be difficult because exceptions occur on different threads from the assembly of the chain, and reactive stack traces are often unclear.

Core Features & Use Cases

  • Reactor debugging fundamentals: using log(), checkpoint(), Hooks.onOperatorDebug, and ReactorDebugAgent to illuminate signal flow and stack traces.
  • Diagnosing common reactive issues: empty signal, timeouts, backpressure, context loss across schedulers, and hidden errors in saga or command pipelines.
  • Practical guidance and examples for tracing errors across CommandBus, QueryBus, EDA, and saga orchestration.

Quick Start

Enable Reactor debugging at startup (e.g., Hooks.onOperatorDebug or ReactorDebugAgent) and review logs and checkpoints to identify the failing operator in the reactive chain.

Frequently Asked Questions about debugging-reactive-chains

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

FAQPage Schema
How do I debug unclear stack traces in Reactor reactive chains?▼

Debug unclear Reactor stack traces by enabling Hooks.onOperatorDebug or ReactorDebugAgent at startup to illuminate signal flow and pinpoint the failing operator in the reactive chain.

Why does my Reactor pipeline lose context across different schedulers?▼

Reactor pipelines lose context across schedulers when context propagation fails during thread transitions; using checkpoint() and log() helps trace signal flow and diagnose the exact operator where context drops.

What is the best way to trace hidden errors in saga and CommandBus pipelines?▼

Trace hidden errors in saga and CommandBus pipelines by applying log() and checkpoint() operators to expose signal flow, revealing timeouts, backpressure issues, and empty signals within reactive orchestration.

How do I diagnose empty signals and timeouts in reactive pipelines?▼

Diagnose empty signals and timeouts in reactive pipelines by inserting checkpoint() markers and log() operators to monitor signal completion states and identify blocking operators causing the delay.

When do I need ReactorDebugAgent for Firefly Framework services?▼

You need ReactorDebugAgent for Firefly Framework services when exceptions occur on different threads from chain assembly, making reactive stack traces unclear during CommandBus, QueryBus, and EDA flow development.

Related Skills

Explore More Software Engineering Skills→
aalmadaaalmada
15

scaffold-aggregate

Scaffold event-sourced aggregates with Apply methods and Marten configuration.

Community
Advanced
jarrodmedranojarrodmedrano
2

level-design

Provide a level-design consulting framework for spatial layouts, player guidance, and pacing.

Community
Basic
hieutrtrhieutrtr
8

monitoring-setup

Implement logging, metrics, tracing, health checks, alerting, and dashboards for Python/React services.

Community
Advanced
JackSmack1971JackSmack1971

debug-root-cause-analysis

Guide structured root-cause debugging through observe, reproduce, hypothesize, test, fix, verify, and prevent phases.

Community
Advanced