label-audit

Name: label-audit
Availability: InStock
Author: nolanvenhola

Audit and verify label and address usage in Zeliard assembly code.

3|Updated Feb 1, 2026

Search Tags:#static analysis #code audit #assembly code #label auditing #Zeliard

Ready to run

npx skills add https://github.com/nolanvenhola/zeliard --skill label-audit-nolanvenhola

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: label-audit
Source: https://github.com/nolanvenhola/zeliard/tree/main/.claude/skills/label-audit
Command: npx skills add https://github.com/nolanvenhola/zeliard --skill label-audit-nolanvenhola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grep, sed, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of auditing and verifying label and address usage in Zeliard assembly code, enhancing code clarity and accuracy.

Core Features & Use Cases

Static Analysis: Perform deep static analysis to understand label and address usage patterns.
Usage Tracing: Trace the usage of labels and addresses across multiple files.
Verification: Ensure bit-perfect SAR builds after making changes to labels and addresses.
Use Case: When reviewing the Zeliard codebase, use this Skill to identify and correct misnamed labels or addresses, ensuring that the code accurately reflects the intended logic.

Quick Start

Audit the label 'gvar_flag_FFNN' using the label-audit skill.

Frequently Asked Questions about label-audit

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

FAQPage Schema

How do I audit labels and addresses in Zeliard assembly code?▼

You can automate static analysis to trace label and address usage across multiple Zeliard assembly files, identifying misnamed labels and verifying bit-perfect SAR builds to ensure code accuracy.

What is label auditing for assembly codebases?▼

Label auditing performs static analysis on assembly code to trace label and address usage across multiple files, identifying misnamed labels to maintain code clarity and accurate logic.

Do I need python and grep to trace assembly code labels?▼

Yes, tracing assembly labels requires grep, sed, and python to automate static analysis. These dependencies allow you to search files, manipulate text, and run scripts to track usage and verify SAR builds.

Why does my SAR build fail after changing assembly labels?▼

SAR builds fail after label changes due to misnamed labels or incorrect address references across files. Auditing identifies these mismatches through static analysis and verifies usage traces to ensure bit-perfect builds.

Can I trace label usage across multiple assembly files?▼

Yes, you can trace label usage across multiple assembly files using static analysis. This tracks references throughout the codebase, identifies misnamed labels, and verifies address alignment before completing SAR builds.