task-investigate-bug

To investigate a cross-repo UI bug, submit the bug description and reproduction steps to this skill. It orchestrates analysis across both frontend and backend codebases, gathers logs, and generates a concise diagnostic report.

Yes, you can find the root cause without manual code inspection by applying this skill. It coordinates an investigation agent to locate relevant code paths and determine whether the defect originates in the UI layer, the API, or data handling logic.

Cross-repo bug diagnosis is the process of tracing a reported defect across multiple project repositories. This skill automates the investigation by gathering logs, stack traces, and UI error screenshots from both frontend and backend codebases.

You generate a diagnostic report by providing the tester's bug description and reproduction steps to the skill. It then collects relevant context and produces a concise summary with suggested next steps for developers.

Yes, this bug investigation skill works with both frontend and backend codebases. It is specifically designed to handle UI-reported issues that span both layers, coordinating cross-repo analysis to identify where the defect originates.

Automated cross-repo bug investigation relies on the provided bug description and reproduction steps to function effectively. Without accurate reproduction steps or accessible logs, the skill may struggle to locate the exact root cause across the project repository.