ai-ad-code-verifier

Verify ad-code integration for cross-module boundary and API violations.

Updated Nov 8, 2025
One-click install
npx skills add https://github.com/wade56754/AI_ad_spend02 --skill ai-ad-code-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-ad-code-verifier
Source: https://github.com/wade56754/AI_ad_spend02/tree/main/.claude/skills/ai-ad-code-verifier
Command: npx skills add https://github.com/wade56754/AI_ad_spend02 --skill ai-ad-code-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies code against SoT constraints with multi-layer checks, detects hallucinations, and auto-fixes issues when possible.

Core Features & Use Cases

  • 8-layer verification: Boundary, hallucination, AST, compliance, integration, tests, and more.
  • Anti-hallucination: Flags non-existent APIs or modules and ensures import validity.
  • Use Case: Validate a generated module against SoT before integration.

Quick Start

Provide generated code and relevant SoT references; the verifier returns issues and suggested fixes.

Frequently Asked Questions about ai-ad-code-verifier

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

FAQPage Schema
How do I verify generated code against source-of-truth constraints before integration?

Code verification checks generated modules against SoT constraints using multi-layer analysis. This Skill applies 8-layer verification—boundary checks, hallucination detection, AST validation, compliance rules, and integration readiness—to flag violations like cross-module writes, nonexistent imports, and syntax errors before code submission, blocking failures until resolved.

What is anti-hallucination in code verification and why does it matter?

Anti-hallucination detection flags non-existent APIs, modules, and invalid imports that can occur in generated code. This Skill identifies these hallucinations during verification so they're caught before integration, ensuring only valid, traceable imports and module references reach production.

Can this verify code across multiple modules for boundary violations?

Yes. This Skill verifies multi-module code pipelines (pitcher, finance, ad_account, project) to detect cross-module write violations and boundary breaches. It validates that modules respect module boundaries and SoT compliance rules across the entire codebase during automated builds.

How does static analysis catch finance-rule noncompliance and SoT violations?

Static analysis via AST parsing and rule-based checks detects finance-rule noncompliance and SoT violations by examining code structure without execution. This Skill applies finance-specific and SoT compliance rules to generated code, reporting violations with suggested fixes.

What happens if code verification fails—does it block deployment?

Yes. Verification failures block code submission and automated builds. The Skill reports issues with complete source traceability and suggested fixes; code must resolve all violations before proceeding to integration.

Does this verify test coverage and integration readiness alongside syntax checking?

Yes. Beyond syntax and AST validation, this Skill checks test coverage validation and integration readiness, ensuring generated code meets all requirements—boundary compliance, hallucination absence, finance rules, and deployability—before integration.