跳转到主要内容
此内容尚未提供您的语言版本,正在以英文显示。

Root Cause Tracing

技能 已验证 活跃
属于:Kaizen

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

目的

To help developers efficiently diagnose and fix bugs by tracing their origin backward through the execution flow, rather than just addressing the symptoms where they appear.

功能

  • Systematic backward call stack tracing
  • Techniques for adding runtime instrumentation
  • Guidance on finding test-case polluters
  • Illustrative examples of root cause analysis

使用场景

  • When errors occur deep in the execution stack.
  • To pinpoint the origin of invalid data in complex call chains.
  • To identify the specific test case causing unexpected behavior.
  • When traditional debugging methods at the symptom point are insufficient.

非目标

  • Fixing bugs solely at the point of manifestation (the symptom).
  • Providing general debugging tools without a focus on backward tracing.
  • Automated bug fixing without user-guided investigation.

Code Execution

  • info:LoggingThe skill suggests using `console.error()` for debugging during tests, which provides some level of logging for diagnostic purposes.

安装

请先添加 Marketplace

/plugin marketplace add NeoLabHQ/context-engineering-kit
/plugin install kaizen@context-engineering-kit

质量评分

已验证
99 /100
1 day ago 分析

信任信号

最近提交9 days ago
星标993
许可证GPL-3.0
状态
查看源代码