investigate

Diagnose user-reported symptoms by mapping them to diagnostic tools and analyzing logs.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill investigate-cwilliams5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/investigate
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill investigate-cwilliams5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides the diagnosis of user-reported symptoms or bugs by mapping them to appropriate diagnostic tools, collecting necessary data, and analyzing the results to pinpoint the root cause.

Core Features & Use Cases

  • Symptom Classification: Categorizes user-reported issues (e.g., keyboard, focus, window list) to identify relevant diagnostic tools.
  • Data Collection Guidance: Instructs users on enabling specific diagnostics (e.g., FlightRecorder, EventLog) and provides clear reproduction steps.
  • Data Analysis: Correlates data from multiple sources (FlightRecorder, logs) to diagnose issues and suggest solutions or escalations.
  • Use Case: A user reports that Alt-Tab is not working correctly. This Skill will guide them to enable specific logging, reproduce the issue, and then analyze the collected logs to determine if it's a keyboard hook problem, a focus issue, or a workspace synchronization error.

Quick Start

Use the investigate skill to help a user diagnose why their window list is not updating correctly.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I diagnose user-reported keyboard input and window focus issues?

Diagnose keyboard input and window focus issues by enabling FlightRecorder and WinEventLog, reproducing the reported scenario, and correlating the collected diagnostic data to identify the root cause of the malfunction.

What is the process for troubleshooting window list and workspace synchronization errors?

Troubleshooting window list and workspace synchronization errors requires classifying the reported symptom, enabling KomorebiLog and IPCLog diagnostics, and analyzing the collected data to identify the root cause.

How do I collect and analyze diagnostic logs for overlay rendering and icon bugs?

Collect and analyze logs for overlay rendering and icon bugs by enabling PaintTimingLog and IconPumpLog, reproducing the issue, and correlating the recorded data to trace the rendering or icon pipeline failure.

Can I use this diagnostic approach for startup failures and configuration editor problems?

Yes, you can use this diagnostic approach for startup failures and configuration editor problems by enabling ProcPumpLog and StoreLog, reproducing the issue, and analyzing the correlated data to determine the root cause.

What are the limitations when diagnosing bypass mode and WebView issues?

Diagnosing bypass mode and WebView issues requires pre-enabling WebViewLog and ChurnLog before the issue occurs, as the tool correlates data from multiple pre-enabled log sources to analyze the root cause effectively.