skills.rest
openharmony
openharmonyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

build-error-analyzer

Analyze OpenHarmony build errors from last_error.log and suggest fixes.

14|8|Updated Oct 29, 2024
Search Tags:#analyze#OpenHarmony#last_error#undefined-symbol#build-error
One-click install
npx skills add https://github.com/openharmony/arkui_ace_engine --skill build-error-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-error-analyzer
Source: https://github.com/openharmony/arkui_ace_engine/tree/main/.claude/skills/build-error-analyzer
Command: npx skills add https://github.com/openharmony/arkui_ace_engine --skill build-error-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill helps engineers diagnose OpenHarmony build failures by analyzing the latest last_error.log generated after extraction from the build logs.

Core Features & Use Cases

  • Error classification: Distinguishes compilation, linking, and build-system errors.
  • Contextual guidance: Matches error patterns with historical cases and suggests concrete fixes.
  • SDK support: Applies to both normal product builds and SDK builds, with SDK-specific paths when relevant.

Quick Start

Use the extraction script to generate last_error.log from the build log: foundation/arkui/ace_engine/.claude/skills/build-error-analyzer/script/extract_last_error.sh out/<product>/build.log Then feed the last_error.log to this skill for analysis and review the suggested fixes.

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 an OpenHarmony build error from the build log?▼

To diagnose an OpenHarmony build error, extract the latest last_error.log from your product's build.log, then feed it to the analyzer. It classifies the error and suggests concrete file modifications and GN changes based on historical cases.

How do I extract last_error.log for OpenHarmony SDK builds?▼

For OpenHarmony SDK builds, run the extraction script against out/sdk/build.log instead of the standard product build.log path to generate the last_error.log file required for error analysis.

What types of build system failures can the OpenHarmony error analyzer identify?▼

The OpenHarmony error analyzer distinguishes compilation, linking, and build-system failures, including SDK-specific build errors, by matching error patterns from last_error.log against historical cases to suggest concrete fixes.

Does the OpenHarmony build error analyzer require any specific environment setup?▼

The OpenHarmony build error analyzer requires no external dependencies, but it mandates an extraction step to generate last_error.log from the raw build log before it can provide contextual guidance and fix recommendations.

What kind of fix recommendations does the analyzer provide for undefined symbol errors?▼

For undefined symbol and other build errors, the analyzer provides targeted fix recommendations including concrete file modifications, GN changes, and verification steps by matching error patterns from last_error.log with historical cases.

Related Skills

Explore More Software Engineering Skills→
sentientspritesentientsprite

trading-analysis

Parse trading bot logs to extract performance metrics and generate Markdown reports.

Community
Intermediate
openharmonyopenharmony
14

openharmony-build

Automate OpenHarmony builds from source with log verification and error analysis.

Official
Advanced
openharmonyinsightopenharmonyinsight
31

build-error-analyzer

Extract and classify OpenHarmony build errors from last_error.log.

Official
Intermediate
eclipse-oniro-mirrorseclipse-oniro-mirrors

build-error-analyzer

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

Official
Advanced