skills.rest
GregorStocks
GregorStocksCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deep-analysis

Trace mage-bench game log bugs to source code and file issue summaries.

64|8|Updated Oct 24, 2025
Search Tags:#issue-tracking#log-analysis#bug-triage#deep-analysis#xmage#bridge-logs
One-click install
npx skills add https://github.com/GregorStocks/mage-bench --skill deep-analysis-gregorstocks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-analysis
Source: https://github.com/GregorStocks/mage-bench/tree/main/.claude/skills/deep-analysis
Command: npx skills add https://github.com/GregorStocks/mage-bench --skill deep-analysis-gregorstocks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep analysis of mage-bench game logs to identify root cause by tracing issues to source code and filing detailed issues for quick remediation.

Core Features & Use Cases

  • End-to-end log triage across chat messages, error logs, bridge logs, and game_events.jsonl to surface root causes.
  • Bootstrap workflow from export data and bootstrap roadmap to roadmap for investigation.
  • Create structured issue summaries and link to relevant logs and code locations.

Quick Start

Claim the most recent unanalyzed game and generate a root-cause report.

Frequently Asked Questions about deep-analysis

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

FAQPage Schema
How do I trace errors in game logs to specific source code locations?▼

To trace bugs to source code, cross-reference game_events.jsonl with error and bridge logs to surface root causes. This deep analysis isolates the failure point and generates a structured issue summary linking problematic logs directly to code locations.

What's the best way to triage bugs across multiple mage-bench game log formats?▼

Triage bugs across mage-bench logs by cross-referencing chat messages, error logs, bridge logs, and game_events.jsonl together. This end-to-end log analysis surfaces the root cause across disparate formats, allowing you to file detailed issues for quick remediation.

How do I bootstrap game log exports for deep root-cause analysis?▼

Bootstrap game log exports by extracting gz files from website/public/games/*.json.gz. This bootstrapping workflow unpacks compressed export data, creating a roadmap to parse game_events.jsonl and supporting logs for investigation.

Can I automatically generate structured issue summaries from game_events.jsonl?▼

Yes, you can generate structured issue summaries from game_events.jsonl. Parsing the jsonl file alongside error and bridge logs surfaces root causes and outputs detailed issue summaries with recommended fixes.

Do I need gz export files to claim and analyze unanalyzed games?▼

Yes, you need gz export files from website/public/games/*.json.gz to claim and analyze unanalyzed games. Deep analysis requires bootstrapping from these gz exports to extract metadata and parse game logs for root-cause reporting.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
112

Prow Job Extract Must-Gather

Extract and decompress nested must-gather archives from Prow CI job artifacts.

Official
Advanced
t-miura-024t-miura-024

mt-analyze-error

Analyze software errors to identify root causes and organize remediation plans.

Community
Intermediate
razorpayrazorpay
31

pr-action-analyzer

Analyze GitHub PR CI failures and generate structured failure reports.

Official
Advanced
Dev-GOMDev-GOM
95

unity-compile-fixer

Diagnose Unity C# compilation errors from VSCode OmniSharp diagnostics and propose fixes.

Community
Advanced