write-patch-as-yaml

Write patch analysis results to a YAML file beside the target binary.

60|11|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill write-patch-as-yaml-hlnd2t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-patch-as-yaml
Source: https://github.com/HLND2T/CS2_VibeSignatures/tree/main/.claude/skills/write-patch-as-yaml
Command: npx skills add https://github.com/HLND2T/CS2_VibeSignatures --skill write-patch-as-yaml-hlnd2t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates persisting patch analysis results to a YAML file placed alongside the target binary using IDA Pro MCP, ensuring reproducible patch data documentation.

Core Features & Use Cases

  • Persist patch targeting details (patch_name, patch_sig, patch_bytes) to a deterministic YAML file named after the patch.
  • Write the YAML next to the binary in the same directory, with optional patch_sig_disp support.
  • Facilitates patch-tracking across analysis sessions by standardizing the YAML format.

Quick Start

After you identify a patch and generate its signature, run the workflow to write the YAML next to the binary.

Frequently Asked Questions about write-patch-as-yaml

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

FAQPage Schema
How do I persist IDA Pro patch analysis results as a YAML file next to the binary?

To persist patch analysis as YAML, you need a known patch name, patch signature, and replacement bytes. The Skill writes these targeting details into a standardized YAML file placed in the same directory as the target binary using IDA Pro MCP.

What format is used to document binary patches for reproducible analysis sessions?

YAML format is used to document binary patches for reproducible analysis sessions. It standardizes patch tracking data, including patch_name, patch_sig, and patch_bytes, ensuring consistent documentation across analysis workflows.

Do I need IDA Pro MCP to write patch signatures and replacement bytes to YAML?

Yes, IDA Pro MCP is required to write patch signatures and replacement bytes to YAML. You must also supply a known patch name, patch signature, and replacement bytes before the YAML generation can execute.

Can I include a display signature when saving patch data to YAML beside the target binary?

Yes, you can include a display signature when saving patch data to YAML beside the target binary. The process supports optional patch_sig_disp alongside the required patch name, signature, and replacement bytes.

What is the best way to track binary patches across multiple IDA Pro analysis sessions?

The best way to track binary patches across sessions is persisting them as a deterministic YAML file named after the patch. This standardizes patch data next to the binary, ensuring reproducible documentation for future reference.

Why are my patch analysis results not saving to YAML beside the binary?

Patch analysis results fail to save to YAML if required inputs are missing. You must provide a known patch name, patch signature, and replacement bytes, and ensure IDA Pro MCP is configured properly to generate the file.