analyze-benchmark

Analyze benchmark logs to determine build success and migration issues.

1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/weidongxu-microsoft/java-update-examples --skill analyze-benchmark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-benchmark
Source: https://github.com/weidongxu-microsoft/java-update-examples/tree/main/.github/skills/analyze-benchmark
Command: npx skills add https://github.com/weidongxu-microsoft/java-update-examples --skill analyze-benchmark

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the analysis of benchmark logs, providing a clear summary of build statuses and migration-related issues.

Core Features & Use Cases

  • Build Status Analysis: Determines if builds passed or failed.
  • Dependency Change Tracking: Analyzes changes in dependencies, specifically checking for the removal of legacy dependencies.
  • Migration Issue Identification: Identifies potential issues during the migration process from evaluation reports.
  • Use Case: After running a benchmark for a code migration, use this Skill to quickly understand which test cases failed, why they failed, and if the dependency migration was successful.

Quick Start

Analyze the benchmark logs in the 'benchmark_log' folder.

Frequently Asked Questions about analyze-benchmark

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

FAQPage Schema
How do I analyze benchmark logs to determine build success or failure?

To analyze benchmark logs, this Skill processes unzipped local files to determine build success or failure. It identifies causes of build failures and checks dependency changes, outputting a SUMMARY.md report aggregating findings for each case.

How do I track dependency changes and identify migration issues from benchmark logs?

To track dependency changes, this Skill analyzes successful benchmark builds for dependency modifications, specifically checking for the removal of legacy dependencies. It also identifies potential migration issues from evaluation reports and aggregates them.

What is the best way to aggregate benchmark build status results into a single report?

The best way to aggregate benchmark build status results is using this Skill to generate a SUMMARY.md report. It automatically aggregates findings for each case output, summarizing build statuses, dependency changes, and migration issues.

Do I need to unzip benchmark logs before analyzing build failures and dependency changes?

Yes, you need to unzip benchmark logs before analysis. This Skill requires unzipped local files placed in a folder to process the build status, identify causes of failures, and analyze dependency migration successfully.

Why does my benchmark build fail during a code migration and how can I identify the cause?

Benchmark builds fail during code migration due to dependency or configuration issues. This Skill identifies causes of build failures by analyzing local unzipped benchmark logs and highlights removal of legacy dependencies in successful builds.