symbol-sweep

Audit cross-file symbolic references and replace hardcoded operands in Zeliard TASM assembly source.

3|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/nolanvenhola/zeliard --skill symbol-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symbol-sweep
Source: https://github.com/nolanvenhola/zeliard/tree/main/.claude/skills/symbol-sweep
Command: npx skills add https://github.com/nolanvenhola/zeliard --skill symbol-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the cross-file symbol audit and bulk hardcoded-reference cleanup for the Zeliard TASM source code, saving time and reducing human error.

Core Features & Use Cases

  • Cross-File Symbol Drift Detection: Identifies and resolves inconsistencies in symbolic references across multiple files.
  • Bulk Hardcoded Reference Cleanup: Replaces raw operands with symbolic equivalents in a single pass.
  • Driver Dispatch Table Mapping: Automates mapping of driver dispatch tables and resolving conflicting references.
  • Use Case: When working on a large codebase with many interdependent files, this Skill can help maintain consistency and improve readability.

Quick Start

Run the 'symbol-sweep' skill to start a symbol sweep across the Zeliard TASM source code.

Frequently Asked Questions about symbol-sweep

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

FAQPage Schema
How do I automate cross-file symbol auditing for TASM assembly source code?

Cross-file symbol auditing for TASM assembly source code can be automated by scanning multiple files to identify symbolic reference inconsistencies and replacing raw operands with symbolic equivalents in a single pass.

What is the best way to clean up hardcoded references in assembly language files?

Cleaning up hardcoded references in assembly language files involves replacing raw operands with their symbolic equivalents across interdependent files, ensuring consistency and improving overall codebase readability.

Can I map driver dispatch tables automatically in Zeliard source code?

Yes, driver dispatch tables in Zeliard source code can be mapped automatically by resolving conflicting references and structuring the dispatch logic to maintain symbolic integrity across TASM files.

What causes symbolic reference drift across multiple assembly files?

Symbolic reference drift across multiple assembly files occurs when interdependent source files are updated independently, causing inconsistencies that require cross-file analysis to identify and resolve mismatched symbolic references.

Do I need static analysis tools to perform a bulk symbol audit on assembly source code?

Yes, performing a bulk symbol audit on assembly source code requires static analysis tools to verify code integrity and accurately map symbolic references across the entire codebase.