debug-diff

Diagnose failed diffyscan verification runs by analyzing diffs and logs.

142|19|Updated Apr 22, 2023
One-click install
npx skills add https://github.com/lidofinance/diffyscan --skill debug-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-diff
Source: https://github.com/lidofinance/diffyscan/tree/main/.claude/skills/debug-diff
Command: npx skills add https://github.com/lidofinance/diffyscan --skill debug-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers diagnose and troubleshoot failed diffyscan verification runs by analyzing diffs, logs, and reports to identify root causes and guide remediation steps.

Core Features & Use Cases

  • Analyze failing runs to pinpoint where diffs, misconfigurations, or explorer metadata diverge from expectations.
  • Inspect digest logs and HTML diff reports to understand the failure context and affected contracts.
  • Generate actionable remediation steps and a path to re-run the investigation with a corrected config or contract address.

Quick Start

Provide the failing config path or contract address to begin diagnosing the issue.

Frequently Asked Questions about debug-diff

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

FAQPage Schema
How do I debug a failed diffyscan verification run?

Diagnose a failed diffyscan run by providing the config path or contract address, allowing the Skill to inspect digest logs and HTML diff reports to identify where misconfigurations or explorer metadata diverge from expectations.

Why does my blockchain contract verification show unexpected diffs?

Unexpected diffs arise when local configuration mismatches explorer metadata. Analyzing the per-run digest directory and HTML diff reports reveals the exact contract divergence and guides the required configuration corrections.

What do I need to diagnose a non-zero exit code from a diffyscan run?

You need access to the digest directory, per-run diff reports, and the relevant config or contract address. These inputs allow the Skill to analyze the failure context and generate actionable remediation steps.

Can I use diff analysis to troubleshoot explorer metadata mismatches?

Yes, diff analysis inspects HTML diff reports and digest logs to understand the failure context, pinpointing exactly where affected contracts diverge from the expected explorer metadata and local configuration.

What is the best way to resolve misconfigurations found in blockchain diff reports?

Analyze digest logs to pinpoint the failure context, apply the generated actionable remediation steps, and re-run the investigation using a corrected config path or contract address to verify the fix.