Verified:GitHub

maaend-issue-log-analysis

Name: maaend-issue-log-analysis
Availability: InStock
Author: MaaEnd

Fetch and decompress MaaEnd-logs-*.zip attachments from GitHub issues to extract evidence and produce diagnostic reports.

3.6k|298|Updated Mar 18, 2022

Search Tags:#root-cause #log-analysis #issue-analysis #maaend #maa-framework #mxu #dmp-analysis

Ready to run

npx skills add https://github.com/MaaEnd/MaaEnd --skill maaend-issue-log-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maaend-issue-log-analysis
Source: https://github.com/MaaEnd/MaaEnd/tree/main/.claude/skills/maaend-issue-log-analysis
Command: npx skills add https://github.com/MaaEnd/MaaEnd --skill maaend-issue-log-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MaaEnd issue analysis is a structured workflow that automatically gathers and interprets public issue artifacts from MaaEnd/MaaEnd, including MaaEnd-logs-*.zip attachments, to reveal root causes and proposed fixes.

Core Features & Use Cases

Automatically fetch and decompress MaaEnd-logs-.zip from issues and extract key evidence from logs such as maa.log, maa.bak.log, go-service.log, mxu-tauri.log, mxu-web-.log, mxu-agent*.log, config/*, and on_error/.
Correlate evidence with MaaEnd, MaaFramework, and MXU documentation to derive root causes and actionable remediation plans for issues like task stalls, misrecognitions, controller mismatches, and pipeline failures.
Produce a consolidated diagnostic report with timelines, validated evidence, and recommended fixes to guide users or developers when analyzing MaaEnd issues and logs.

Quick Start

Provide an issue URL or number (e.g., https://github.com/MaaEnd/MaaEnd/issues/1234) to start the analysis.

Frequently Asked Questions about maaend-issue-log-analysis

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

FAQPage Schema

How do I analyze MaaEnd issue logs to find the root cause of task stalls?▼

Analyze MaaEnd issue logs by fetching MaaEnd-logs-*.zip attachments from GitHub issues, decompressing them, and cross-referencing logs like maa.log and mxu-tauri.log with documentation to pinpoint root causes. This extracts evidence to identify task stalls and pipeline failures.

What is the process for extracting diagnostic evidence from MaaEnd-logs zip files?▼

Extracting diagnostic evidence from MaaEnd-logs involves decompressing the zip file and parsing key logs such as go-service.log, mxu-web-*.log, and on_error/ directories. This process surfaces timelines, controller mismatches, and task names for root cause analysis.

Can I use a GitHub issue URL to automatically diagnose MaaFramework pipeline failures?▼

Yes, you can use a GitHub issue URL to automatically diagnose MaaFramework pipeline failures. Providing the issue URL allows the workflow to automatically fetch and extract log artifacts to identify version, controller, and task name details for remediation.

Which log files are required to troubleshoot MXU controller mismatches and misrecognitions?▼

Troubleshooting MXU controller mismatches requires log files like maa.log, go-service.log, mxu-tauri.log, mxu-agent*.log, and on_error/ directories. These logs are cross-referenced with MaaEnd and MaaFramework documentation to derive actionable fixes for misrecognition issues.

Why does my MaaEnd issue analysis fail when the MaaEnd-logs attachment is missing?▼

MaaEnd issue analysis fails when the MaaEnd-logs attachment is missing because the workflow relies on decompressing MaaEnd-logs-*.zip to extract evidence from logs like maa.log. Without these logs, it cannot cross-reference documentation to produce a structured diagnostic report.

What is the best way to generate a structured diagnostic report for MaaEnd issues?▼

The best way to generate a structured diagnostic report for MaaEnd issues is to normalize inputs, extract timelines from logs, and cross-reference evidence with MaaEnd, MaaFramework, and MXU documentation. This produces a consolidated report with validated evidence and recommended fixes.