vm-compat-triage

Triage analyze-op-program-client CI failures by analyzing syscall and opcode findings.

6.5k|4.0k|Updated Feb 6, 2020
One-click install
npx skills add https://github.com/ethereum-optimism/optimism --skill vm-compat-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vm-compat-triage
Source: https://github.com/ethereum-optimism/optimism/tree/main/.claude/skills/vm-compat-triage
Command: npx skills add https://github.com/ethereum-optimism/optimism --skill vm-compat-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of triaging failures in the analyze-op-program-client CI job, which checks for compatibility issues between the OP Stack VM and Cannon.

Core Features & Use Cases

  • Automated Failure Analysis: Identifies new syscall or opcode findings that cause CI jobs to fail.
  • Reachability Determination: Helps determine if flagged findings are actually reachable during runtime.
  • Baseline Management: Assists in updating the compatibility baseline to reflect current code.
  • Use Case: When a pull request causes the vm-compat CI job to fail, this Skill can be used to quickly analyze the new findings, determine their validity, and update the baseline, allowing the PR to proceed.

Quick Start

Use the vm-compat-triage skill to triage the vm-compat failure on the provided pull request.

Frequently Asked Questions about vm-compat-triage

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

FAQPage Schema
How do I triage vm-compat CI failures in op-program?

The vm-compat-triage process automates failure analysis by identifying new syscall or opcode findings that cause CI jobs to fail. It determines if flagged findings are actually reachable during runtime before updating the compatibility baseline.

What causes analyze-op-program-client CI jobs to fail?

Analyze-op-program-client CI jobs fail when new syscall or opcode findings are detected during vm-compat analysis of op-program client code, indicating compatibility issues between the OP Stack VM and Cannon.

Do I need GitHub CLI and jq to analyze OP Stack VM compatibility?

Yes, analyzing OP Stack VM compatibility failures requires GitHub CLI, jq, the vm-compat binary, and llvm-objdump. These dependencies are required within Linux environments to process findings and update baselines.

How does runtime reachability determination work for opcode findings?

Runtime reachability determination evaluates whether newly flagged opcode or syscall findings are actually executed during runtime. This helps filter out unreachable findings and validate only the compatibility issues that impact the OP Stack VM.

When do I need to update the compatibility baseline for OP Stack?

You need to update the compatibility baseline when a pull request introduces valid, reachable syscall or opcode findings. Updating the baseline reflects the current code and allows the PR to proceed despite the vm-compat CI failure.