state-diff

Diff register and memory changes from before/after state snapshots.

196|17|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/dariushoule/x64dbg-skills --skill state-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-diff
Source: https://github.com/dariushoule/x64dbg-skills/tree/main/skills/state-diff
Command: npx skills add https://github.com/dariushoule/x64dbg-skills --skill state-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff two debuggee state snapshots to identify register and memory changes between two points in time, enabling precise post-mortem analysis and debugging.

Core Features & Use Cases

  • Compare before/after snapshot data to produce per-register diffs.
  • Detect added, removed, resized, or modified memory regions with byte-level detail.
  • Generate a diff_report.json and a narrative summary to support debugging, reverse engineering, and forensic analysis.

Quick Start

Run the state-diff tool to compare two captured snapshots and generate diff_report.json.

Frequently Asked Questions about state-diff

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

FAQPage Schema
How do I diff debuggee state snapshots to identify register and memory changes?

Diffing debuggee state snapshots requires reading registers.json and memory_map.json from before and after directories. The tool computes per-register differences and detects added, removed, resized, or modified memory regions to pinpoint changes between two points in time.

What is the best way to detect added or resized memory regions during malware analysis?

Detecting added or resized memory regions during malware analysis is done by diffing before and after memory maps. This approach identifies byte-level memory modifications, generating a structured diff_report.json with a summary of all memory region alterations.

How do I compare registers.json files to produce a per-register diff?

Comparing registers.json files involves reading the captured register states from two separate snapshot directories. The tool computes the exact per-register differences between the before and after states, outputting the results into a structured diff_report.json.

Can I use memory map diffing for post-mortem debugging and forensic analysis?

Memory map diffing is highly effective for post-mortem debugging and forensic analysis. By comparing two captured snapshots, it detects byte-level memory changes and generates a narrative summary to support reverse engineering and precise forensic investigations.

What format do I need to capture before running a state snapshot diff?

Running a state snapshot diff requires capturing registers.json and memory_map.json files. You must save these files into separate before and after directories to ensure the tool can accurately read and compare the two debuggee states.