task-investigate-bug

Name: task-investigate-bug
Availability: InStock
Author: foxsilou

Investigate reported UI bugs across frontend and backend codebases.

Updated Apr 1, 2026

Search Tags:#investigation #frontend #backend #diagnostic #bug #cross-repo

Ready to run

npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill task-investigate-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-investigate-bug
Source: https://github.com/FoxSilou/ConfigurationClaude/tree/main/.claude/skills/task-investigate-bug
Command: npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill task-investigate-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI‑reported issues that affect both the frontend and backend often require time‑consuming manual analysis across multiple repositories. This Skill streamlines that process by coordinating an investigation agent to locate root causes and relevant code paths.

Core Features & Use Cases

Cross‑repo analysis: Gathers information from both frontend and backend codebases.
Log and context collection: Retrieves relevant logs, stack traces, and UI error screenshots.
Diagnostic report: Produces a concise summary with suggested next steps for developers.
Use case: When a tester submits a bug description with reproduction steps, the skill quickly identifies whether the defect originates in the UI layer, the API, or data handling logic.

Quick Start

Ask the investigate-bug skill to examine the reported issue and provide a root cause analysis.

Frequently Asked Questions about task-investigate-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate a UI bug across frontend and backend repositories?▼

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.

Can I find the root cause of a reported issue without manual code inspection?▼

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.

What is cross-repo analysis for bug diagnosis?▼

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.

How do I generate a diagnostic report from bug reproduction steps?▼

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.

Does this bug investigation skill work with both frontend and backend codebases?▼

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.

What are the limitations of automated cross-repo bug investigation?▼

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.