Parse Cocos Creator project.log for errors, warnings, and stack traces.
npx skills add https://github.com/eaglhuang/cocos_new --skill cocos-log-reader
Please help me install this Agent Skill. Skill: cocos-log-reader Source: https://github.com/eaglhuang/cocos_new/tree/main/.agents/skills/cocos-log-reader Command: npx skills add https://github.com/eaglhuang/cocos_new --skill cocos-log-reader
This skill helps developers quickly diagnose runtime issues by reading and analyzing the Cocos Creator project.log for errors, warnings, and stack traces. It is the recommended first step before deeper debugging sessions, especially for bug reports, crashes, UI glitches, and initialization failures.
Describe the runtime symptom and I will analyze the latest project.log to surface errors and stack traces.
High-intent search queries and answers about installing and using this skill.
To diagnose a Cocos Creator runtime crash, parse the project.log to capture console outputs and examine stack traces. Filtering log entries by error keywords like TypeError or undefined isolates the root cause of the crash.
Finding the root cause of UI glitches in Cocos Creator involves reading the project.log to filter for warnings and errors. Analyzing stack traces reveals specific mount failures in components like CompositePanel or ChildPanel.
Extracting stack traces from Cocos logs to fix initialization failures requires parsing the project.log file. The skill filters runtime logs by specific symptoms and keywords, preserving session history to surface actionable trace insights.
Yes, this log analysis approach works for missing assets and screen wiring problems. By reading the Cocos Editor Preview log, it captures console errors and warnings, guiding targeted fixes for complex screen routing and initialization issues.
You can filter Cocos runtime logs by specific error keywords like null or undefined. The skill reads the project.log file, isolating these symptoms within stack traces to identify the exact source of runtime errors.
Reading the project.log before a deeper Cocos debugging session surfaces immediate errors and warnings. It is the recommended first step for bug reports, capturing historical console outputs to pinpoint stack traces quickly.
tense-iInstall and configure the cocos-mcp-server MCP extension in Cocos Creator projects.
a1076559139Document XForge2 framework usage for Cocos Creator 3.8 development.
dyCuong03Automate Cocos Creator 3.8.x playable scene, prefab, and asset hierarchy construction.
MarbleSodasControl the V8 inspector to debug Node.js runtime state with breakpoints and expression evaluation.
