cocos-bug-triage

Coordinate screenshot capture and log analysis to triage Unity/Cocos UI bugs.

3|Updated Mar 6, 2026

Search Tags:#unity #screenshot #log-analysis #visual-analysis #cocos #bug-triage #debugging-workflow

Ready to run

npx skills add https://github.com/eaglhuang/cocos_new --skill cocos-bug-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cocos-bug-triage
Source: https://github.com/eaglhuang/cocos_new/tree/main/.agents/skills/cocos-bug-triage
Command: npx skills add https://github.com/eaglhuang/cocos_new --skill cocos-bug-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an end-to-end bug investigation workflow by combining visual verification (screenshot) with log analysis (log-reader) to accelerate triage for reports that include both UI symptoms and runtime errors.

Core Features & Use Cases

Orchestrates cocos-screenshot and cocos-log-reader into a single triage pipeline to replace manual evidence collection.
Defines a phase-driven process: Visual Confirmation, Log Analysis, Root-Cause Localization, Fix & Validation.
Ideal for bugs in UI-heavy scenarios such as CompositePanel / ChildPanel mounts, screen wiring issues, or battle scene UI crashes.

Quick Start

Initiate the bug triage workflow by capturing a screenshot of the failing UI, then run log analysis to identify the root cause.

Frequently Asked Questions about cocos-bug-triage

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

FAQPage Schema

How do I triage UI bugs in Cocos or Unity using screenshots and runtime logs?▼

Bug triage for UI-heavy defects combines visual confirmation from screenshots with log analysis to pinpoint root causes. This workflow automates evidence collection across Cocos and Unity projects to accelerate debugging.

What is the best way to find the root cause of a CompositePanel or ChildPanel UI crash?▼

Root cause localization for CompositePanel or ChildPanel crashes uses a phase-driven workflow to correlate visual UI defects with runtime log errors. It systematically links screenshot evidence to log anomalies to find the exact failure point.

How do I start debugging a battle scene UI crash when I have both a screenshot and an error log?▼

Start debugging a battle scene UI crash by running a deterministic, phase-driven workflow that first captures a screenshot of the failing UI, then runs log analysis to correlate visual symptoms with runtime errors for root cause localization.

Does this bug triage workflow support both Cocos and Unity projects?▼

Yes, the bug triage workflow supports both Cocos and Unity projects. It is designed to handle UI-heavy defect scenarios, including screen wiring issues and battle scene crashes, across both game engines.

Can I use this log analysis workflow for screen wiring issues without manual evidence collection?▼

Yes, you can replace manual evidence collection by orchestrating screenshot capture and log reading into a single triage pipeline. This workflow automatically correlates visual UI symptoms with runtime logs to resolve screen wiring issues.

What are the limitations of using a phase-driven workflow for visual bug triage?▼

The phase-driven workflow is limited to UI-heavy defects and requires both screenshots and runtime logs to function effectively. It is not suitable for non-visual bugs or scenarios where log data is unavailable.