tapd-bug-analyzer_skill

Overview

This skill automates analysis and localization of issues reported in TAPD Bug tickets. It supports multiple analysis strategies to extract trace IDs, request URLs with timestamps, or perform code-level investigation when logs are not directly available. The skill returns a structured diagnostic report with error summary, call chain, root cause and remediation suggestions.

How this skill works

The skill parses the TAPD Bug URL to extract workspace_id and bug_id, then fetches the bug details using the TAPD MCP tool. It inspects the bug description and chooses one of three strategies: extract a traceId and query trace logs, extract a timestamped request URL to recover traceIds from gateway logs, or run codebase retrieval and logic analysis when no trace information exists. Once a traceId or relevant code location is found, it runs a log-trace analyzer to build a sorted call chain, surface errors/exceptions, and map logs to code locations for a concise diagnostic report.

When to use it

• You have a TAPD bug link and need rapid root-cause analysis.
• Bug description contains a traceId and you want full call-chain logs.
• Bug description includes a request URL with a timestamp to recover traces.
• Bug has only textual reproduction steps and requires code-level inference.
• You need a structured report with error summary, affected code, and fixes.

Best practices

• Include the full TAPD bug URL when invoking the skill to ensure correct parsing.
• If possible, paste traceId or full request URL (with timestamp) in the bug description for fastest results.
• Provide environment (--env) or allow URL-based environment detection to improve log lookup accuracy.
• When no trace is available, add reproduction steps and relevant identifiers (order id, patient id) to aid code search.
• Review the generated call-chain and code hits to validate inferred root cause before applying fixes.

Example use cases

• Bug contains a 16-character hex traceId — run trace-based analysis to retrieve full logs and exception stacks.
• Bug description has an API URL with a 13-digit timestamp — recover gateway traceId and analyze downstream logs.
• Bug with only reproduction steps — search codebase for related modules and infer likely faulty logic paths.
• Investigate a 500 error reported in test environment by combining TAPD details and sls-trace-analyzer output.
• Locate a missing UI data field by tracing backend prescription handling and pointing to affected Java lines.