Trace data flow and bugs across BrassClaw message, SSE, and tool flows.
npx skills add https://github.com/chtugha/brassclaw --skill trace-chtugha
Please help me install this Agent Skill. Skill: trace Source: https://github.com/chtugha/brassclaw/tree/main/.bob/skills/trace Command: npx skills add https://github.com/chtugha/brassclaw --skill trace-chtugha
This Skill provides a comprehensive tracing mechanism to help diagnose and understand the flow of data and the execution path of functions within the BrassClaw codebase.
Run the 'trace' skill with the symptom or feature name you want to investigate, e.g., 'trace "calendar update error"'
High-intent search queries and answers about installing and using this skill.
To trace data flow and diagnose bugs in the BrassClaw codebase, you can run a dedicated tracing skill with a specific symptom or feature name. This identifies involved files, data transformations, and failure points across the system.
Debugging message flow from user input to LLM response involves analyzing the end-to-end execution path to identify every file and function handling the data. This process maps out data transformations and highlights potential failure points.
Yes, you can analyze SSE event flow and tool flow for debugging BrassClaw applications. The tracing mechanism covers these specific execution paths, helping you understand how events and tools process data throughout the system.
To identify failure points and key files when investigating a BrassClaw issue, execute a trace using the symptom name. This provides a quick reference to the exact functions and files involved in the data transformation.
lyq-linQuery a local knowledge base for Ant Design component semantics and documentation links.
tomgunReproduce bugs with regression tests and apply minimal root-cause fixes.
DisentinelAnalyzes codebases by building and querying a graph database from static analysis.
ps-carvalhoDefine structured logging, metrics, tracing, and alerting patterns for distributed systems.
