hangup-intake

Analyzes HT9045 handler hangup logs and state records to diagnose root causes.

Updated May 28, 2026
One-click install
npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill hangup-intake-hpi-jimmy-chiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hangup-intake
Source: https://github.com/HPI-Jimmy-Chiu/HT904_V899/tree/main/.agents/skills/hangup-intake
Command: npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill hangup-intake-hpi-jimmy-chiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Diagnosing hangup events on HT9045 test handlers requires manually digging through EventLog files, Task_ListWithTime state records, and PickHPRec logs, which is slow and error-prone. This Skill automates the intake and analysis of hangup data to identify suspected modules and root causes. ## Core Features & Use Cases - Automated Log Summarization: Runs analyze_hangup.py to produce a hangup_summary.json containing significant EventLog entries, top error codes, suspicious stuck tasks, and detected anomalies. - Suspected Module Mapping: Maps findings to handler modules such as InArm, OutArm, Shuttle, Index, HotPlate, CatchTray, AutoClean, and ATC, then routes to the corresponding deep-dive sub-skills. - Source Code Correlation: Locates the exact file, line, and function in the V899 source code matching EventLog messages, with an optional error index build for faster lookup. - Use Case: A field engineer receives a hangup folder from an ASE/JCET/SPIL site, runs the analysis, and gets a structured zh-tw report with timeline, evidence, root cause hypotheses, and suggested fixes. ## Quick Start Analyze the latest hangup folder and produce a root cause report with suspected modules and code locations.

Frequently Asked Questions about hangup-intake

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

FAQPage Schema
How do I analyze an HT9045 hangup log folder?▼

Run analyze_hangup.py with the hangup folder path, or use --latest to auto-select the newest folder by modification time. It generates hangup_summary.json with significant EventLog entries, top error codes, stuck tasks, and suspected modules.

What files are needed for hangup root cause analysis?▼

The analysis uses the EventLog text file, Task_ListWithTime.csv state records, and PickHPRec hot plate records from the hangup folder. The script summarizes these into JSON so you avoid reading the large CSV directly.

How does the analysis find the source code location of an error?▼

The summary includes code_locations that automatically map EventLog messages to file, line, and function in the V899 source tree. If matches are missing, build_error_index.py can index roughly 700 cpp/h files for faster lookup.

Which handler modules can be identified as hangup suspects?▼

Suspected modules include InArm, OutArm, Shuttle, Index, HotPlate, CatchTray, AutoClean, and ATC. Each module maps to a dedicated deep-dive sub-skill for further flow-level investigation.

Why should I avoid reading Task_ListWithTime.csv directly?▼

The CSV is very large and consumes excessive context tokens. The analysis script extracts only suspicious stuck tasks and significant state transitions into the JSON summary, which is sufficient for diagnosis.