build-error-analyzer

Extract and categorize OpenHarmony build errors from last_error.log files.

Updated Sep 22, 2023
One-click install
npx skills add https://github.com/eclipse-oniro-mirrors/arkui_ace_engine --skill build-error-analyzer-eclipse-oniro-mirrors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-error-analyzer
Source: https://github.com/eclipse-oniro-mirrors/arkui_ace_engine/tree/main/.claude/skills/build-error-analyzer
Command: npx skills add https://github.com/eclipse-oniro-mirrors/arkui_ace_engine --skill build-error-analyzer-eclipse-oniro-mirrors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers diagnose OpenHarmony build errors by extracting the latest failure block from last_error.log and mapping it against historical cases to provide concrete, actionable fix recommendations. It focuses on guiding users to understand the root cause and suggested remediation without altering code automatically.

Core Features & Use Cases

  • Error extraction: reads out/<product>/last_error.log (SDK builds use out/sdk/last_error.log) to isolate the most recent failure.
  • Error categorization: classifies errors into common types (compilation errors, linker errors, build-system issues) and maps them to known cases in references.
  • Fix recommendations: outputs precise, step-by-step remediation with file paths, commands to verify, and suggested code changes (only guidance, not automatic edits).

Quick Start

Use the extraction script to generate last_error.log from your build output, then review the analysis in out/<product>/last_error.log. For SDK builds, use the out/sdk/last_error.log path.

Frequently Asked Questions about build-error-analyzer

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

FAQPage Schema
How do I diagnose OpenHarmony build errors from last_error.log?

To diagnose OpenHarmony build errors, extract the latest failure block from out/<product>/last_error.log and match it against historical cases to receive precise remediation guidance without modifying code.

What is the best way to fix OpenHarmony SDK build failures?

Fix OpenHarmony SDK build failures by analyzing out/sdk/last_error.log to categorize the error into compilation, linker, or build-system issues and applying the suggested step-by-step remediation.

Can this analyzer automatically edit code to resolve build system issues?

No, the analyzer cannot automatically edit code to resolve build system issues; it focuses on guiding engineers through actionable fixes with file paths and verification commands rather than automated edits.

What types of OpenHarmony compilation errors does the analyzer categorize?

The analyzer categorizes OpenHarmony compilation errors into common types including compilation errors, linker errors, and build-system issues, mapping them to known cases for fix recommendations.

How does matching historical cases help troubleshoot OpenHarmony linker errors?

Matching historical cases helps troubleshoot OpenHarmony linker errors by pattern-matching the extracted failure block against known cases in references to provide concrete, actionable fix recommendations.

Do I need a specific output directory to analyze OpenHarmony build errors?

You need the build output directory containing last_error.log, typically out/<product>/last_error.log for normal builds or out/sdk/last_error.log for SDK builds, to analyze OpenHarmony build errors.

Related Skills