Implements structured, concern-based logging to rapidly identify logic failures in automated tests.
This skill guides developers in implementing the BreakdownLogger pattern, which prioritizes functional 'concerns' over file-based logging. By using a standardized Concerns Map (naming logs after roles like 'gate', 'schema', or 'transition'), it allows for precise filtering and instant identification of where a logic path deviated. It provides strict placement rules (P1-P4) to ensure that inputs, results, and assertion contexts are captured, making it indispensable for debugging complex AI workflows and state-heavy integration tests.
Características Principales
010 GitHub stars
02Automated KEY discovery to prevent naming collisions
03Standardized P1-P4 placement rules for consistent observability
04Integrated validation checks to ensure log quality and prevent production leaks
05Concern-based KEY naming system for intuitive log filtering
06Pre-defined mapping for common test scenarios like schema validation and flow orchestration
Casos de Uso
01Tracing AI intent extraction and decision logic during test failures
02Debugging complex workflow transitions and state machine state changes
03Standardizing logging patterns across large-scale TypeScript test suites
