x-ray

Name: x-ray
Availability: InStock
Author: Auditware

Analyze Solidity codebases to generate structured security readiness reports.

8|Updated Apr 26, 2026

Search Tags:#solidity #smart-contracts #git-history #threat-model #security-analysis #audit-readiness

Ready to run

npx skills add https://github.com/Auditware/auditwizard --skill x-ray-auditware

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: x-ray
Source: https://github.com/Auditware/auditwizard/tree/main/skills/x_ray
Command: npx skills add https://github.com/Auditware/auditwizard --skill x-ray-auditware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generates an x-ray pre-audit security report that condenses threat modeling, invariants, architecture, and git history signals into a single, consumable artifact for protocol reviews.

Core Features & Use Cases

Produces x-ray.md with protocol overview, threat model, invariants, threat profiles, and test-quality signals.
Outputs x-ray/architecture.json and x-ray/entry-points.md to document architecture and entry points.
Reads references/threats.md and references/templates.md to standardize findings and formatting.
Aggregates git-history signals, code ownership, and test coverage indicators for audit readiness.

Quick Start

Run the analysis against the repository to generate x-ray outputs in the x-ray/ directory.

Frequently Asked Questions about x-ray

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

FAQPage Schema

How do I prepare a Solidity codebase for a smart contract security audit?▼

Preparing for a smart contract security audit involves generating a structured readiness report that analyzes Solidity codebases to surface threat models, protocol surfaces, and git history signals into a single consumable artifact for reviewers.

What is threat modeling for smart contracts and how does it identify protocol vulnerabilities?▼

Threat modeling for smart contracts identifies protocol vulnerabilities by mapping entry points and architecture against standard threat templates, producing structured profiles that highlight security risks before a formal review.

Can I use git history signals to assess audit readiness for Solidity smart contracts?▼

Yes, you can use git history signals to assess audit readiness by aggregating code ownership and commit patterns alongside test coverage indicators to evaluate the security posture of Solidity smart contracts.

What's the best way to document smart contract architecture and entry points for security analysis?▼

The best way to document smart contract architecture for security analysis is generating structured outputs like architecture.json and entry-points.md, which map protocol surfaces and guide reviewers through the codebase.

Does pre-audit security analysis require existing test coverage indicators for Solidity protocols?▼

Pre-audit security analysis does not strictly require test coverage but heavily relies on test presence indicators to gauge readiness, surfacing gaps in Solidity protocol testing alongside threat models and architecture visuals.