ludi-audit

Audits Ludi-Bot Python code for 11 targeted failure and data quality issues.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/LudiInformatio/Ludi-Bot --skill ludi-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ludi-audit
Source: https://github.com/LudiInformatio/Ludi-Bot/tree/main/.gemini/skills/ludi-audit
Command: npx skills add https://github.com/LudiInformatio/Ludi-Bot --skill ludi-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill proactively identifies and flags Ludi-Bot-specific failure patterns, silent bugs, and technical debt that generic code reviews would miss, ensuring pipeline stability and data integrity.

Core Features & Use Cases

  • Ludi-Specific Checks: Enforces 11 detailed checks covering pipeline breakers, data quality issues, and technical debt unique to the Ludi-Bot codebase.
  • Targeted Auditing: Focuses on specific areas like BDL abbreviation normalization, canonical data joins, and silent exception handling.
  • Use Case: Before merging a change to the bet_recommendations table, run /ludi-audit review [file(s)] to ensure schema consistency and prevent silent data corruption.

Quick Start

Run the ludi-audit skill on the file utils/mappings.py to check for Ludi-specific gotchas.

Frequently Asked Questions about ludi-audit

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

FAQPage Schema
How do I audit Python code for silent exception swallowing and database connection issues in simulation loops?▼

To audit Python code for silent exception swallowing and database connection issues, you can run an 11-point audit that validates database connection practices within simulation loops and flags silent exception handling.

What does a schema synchronization check for bet_recommendations tables involve?▼

A schema synchronization check for bet_recommendations tables involves validating schema consistency before merging code changes to ensure pipeline stability and prevent silent data corruption.

How do I check Python 3.11 f-string compliance and avoid hardcoded roster data?▼

Checking Python 3.11 f-string compliance and avoiding hardcoded roster data requires an automated audit that detects specific failure patterns and flags technical debt in your Python codebase.

When do I need to run a code review for BDL abbreviation normalization and canonical data joins?▼

You need to run a code review for BDL abbreviation normalization and canonical data joins when preparing to merge changes that affect data quality, ensuring canonical team IDs and composite IDs are handled correctly.

Can I use a targeted code audit to detect technical debt and pipeline breakers before merging?▼

Yes, you can use a targeted code audit to detect technical debt and pipeline breakers before merging by scanning for specific failure patterns like improper player name resolution and inefficient API endpoint selection.