القائمة
Diagnose and fix bugs in Agent Health. Use when a user reports a bug, failing test, or unexpected behavior. Follows a systematic diagnosis → fix → verify workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when instrumenting an application with OpenTelemetry for Agent Health. Provides span structure, required attributes, and config setup for routing traces.
Use when instrumenting an application with OpenTelemetry for Agent Health. Provides span structure, required attributes, and config setup for routing traces.
Add OpenTelemetry instrumentation to an AI agent for Agent Health observability. Use when a user wants to make their agent's traces visible in Agent Health dashboards, or when debugging why traces aren't appearing. Covers span structure, Gen AI semantic conventions, required attributes, and OTLP exporter setup.
Evaluate, benchmark, and improve an AI agent with the Agent Health CLI and server APIs. Use when the user wants to run evaluations/benchmarks, interpret judge results (matcherResults / improvementStrategies), diagnose eval-vs-reality gaps, or raise an agent's pass rate. Mirror of docs/skills/AGENT_HEALTH.md.
Use when the user wants to profile or improve the agent/codebase based on the current session. Profiles this session's traces against a chosen evaluator and proposes concrete edits.
Use when adding, modifying, or debugging agent connectors. Provides connector architecture, built-in types, and custom connector template.
| name | fix-bug |
| description | Diagnose and fix bugs in Agent Health. Use when a user reports a bug, failing test, or unexpected behavior. Follows a systematic diagnosis → fix → verify workflow. |
You are helping the user diagnose and fix a bug in Agent Health.
find_architecture tool to narrow down where the bug likely lives| Symptom | Likely Location |
|---|---|
| Traces not appearing | services/traces/tracePoller.ts, spanCategorization.ts |
| Wrong token/cost metrics | services/traces/metrics.ts |
| Storage errors | services/storage/async*Storage.ts, server/adapters/ |
| CLI command fails | cli/commands/, cli/utils/apiClient.ts |
| SSE stream drops | services/agent/sseHandler.ts, response flushing |
| Evaluation incorrect | server/routes/judge.ts, prompt templates |
| UI not updating | hooks/, services/client/ |
| Agent connector fails | services/connectors/, connector-specific adapter |
Read the relevant code. Look for:
Do NOT guess. Read the code, understand the flow, then identify the root cause.
Apply the minimal fix:
Every bug fix should have a test that would have caught it:
@/ path aliastests/ mirroring the source pathrun_validation tool (scope: "all")git commit -s -m "fix: <concise description of what was wrong>
<one line explaining root cause>"
Update CHANGELOG.md under the appropriate section.