updating-lief

Update the LIEF submodule and audit API compatibility across platforms.

3|1|Updated Nov 8, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-btm --skill updating-lief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: updating-lief
Source: https://github.com/SocketDev/socket-btm/tree/main/.claude/skills/updating-lief
Command: npx skills add https://github.com/SocketDev/socket-btm --skill updating-lief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates updating the LIEF submodule to a stable release tag, audits all LIEF API usage across the repository, and fixes compatibility issues to keep builds green.

Core Features & Use Cases

  • Submodule update orchestration: checkout and pin LIEF to a stable tag and record the new commit.
  • Comprehensive API audit: exhaustively scan all LIEF usage across binject/binpress/bin-infra for compatibility with the new version.
  • Validation & commits: run builds/tests on all platforms, fix issues, and commit with an audit report.

Quick Start

Run the /updating-lief command with a target version to update LIEF, then monitor the automated steps and review the audit report in the final commit.

Frequently Asked Questions about updating-lief

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

FAQPage Schema
How do I update a LIEF submodule and fix API compatibility issues?

To update a LIEF submodule, pin it to a stable release tag, scan all API usage across the repository for compatibility, fix issues, and validate builds and tests before committing with an audit report.

How does API compatibility auditing work when upgrading LIEF?

API compatibility auditing for LIEF exhaustively scans all usage across binject, binpress, and bin-infra directories to identify and fix breaking changes introduced by the new version before validating the build.

Can I run LIEF build and test validation across macOS, Linux, and Windows?

Yes, LIEF build and test validation supports macOS, Linux, and Windows platforms to ensure cross-platform stability after updating the submodule and applying compatibility fixes.

What's the best way to pin a LIEF submodule to a specific release tag?

The best way to pin a LIEF submodule is to checkout the target stable release tag, record the new commit hash, and then proceed with a comprehensive API audit and build validation.

Why does my LIEF build fail after updating the submodule to a new version?

LIEF builds often fail after a submodule update due to API breaking changes, which requires an exhaustive compatibility audit to identify and fix affected calls before re-running tests.