zod-audit

Audit tRPC procedures for missing Zod validation and add schemas.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill zod-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zod-audit
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/zod-audit
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill zod-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for robust input validation in tRPC procedures, preventing runtime errors and security vulnerabilities by ensuring data conforms to expected schemas.

Core Features & Use Cases

  • Audit Existing Validation: Identify and report on tRPC procedures lacking Zod input validation.
  • Add Zod Schemas: Implement Zod schemas for mutation and query procedures, aligning with canonical patterns and reusable schema definitions.
  • Verify iOS Compatibility: Ensure backend validation schemas precisely match the data structures sent from the iOS client, preventing mismatches.
  • Use Case: Automatically scan the HustleXP backend for unvalidated tRPC procedures, prioritize critical financial routers, and add Zod schemas to secure them, ensuring data integrity and preventing common bugs.

Quick Start

Use the zod-audit skill to find all tRPC procedures in the backend that are missing Zod input validation.

Frequently Asked Questions about zod-audit

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

FAQPage Schema
How do I find unvalidated tRPC procedures in my backend?

You can audit tRPC procedures for missing Zod input validation by scanning backend TypeScript code to identify endpoints lacking schemas, prioritizing critical routers like financial mutations to secure data integrity.

How do I ensure tRPC Zod schemas match my iOS client data structures?

To verify iOS compatibility, you correlate backend Zod validation schemas with Swift client implementations to detect and prevent data structure mismatches between the API and mobile client.

Why do I need Zod validation for tRPC mutations and queries?

Zod validation for tRPC procedures prevents runtime errors and API security vulnerabilities by strictly enforcing that incoming data conforms to expected schemas before processing.

Can I add Zod schemas to existing tRPC procedures without breaking the API?

Yes, you can implement Zod schemas for existing mutation and query endpoints by aligning with canonical patterns and reusable schema definitions, ensuring strict validation without altering client-facing behavior.

What is the best way to secure financial tRPC routers with input validation?

The best way to secure financial tRPC routers is to prioritize them during a backend validation audit, immediately applying Zod schemas to enforce strict data integrity on critical transactions.

How do I audit tRPC API security for missing input validation?

You audit tRPC API security by analyzing backend TypeScript code to identify procedures missing Zod input validation, then adding schemas to prevent vulnerabilities and runtime errors.