ki-audit

Detect AI-generated configuration, syntax, and logic errors across code and infrastructure files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill ki-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ki-audit
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/ki-audit
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill ki-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The KI-Audit Skill uncovers typical AI-generated mistakes that block development and operations, such as hallucinated APIs, outdated syntax, incorrect nesting, wrong mappings, and semantic logic errors across configuration, dashboards, and code. It helps teams detect issues that are syntactically valid but semantically incorrect or that were introduced by AI-assisted edits, reducing time spent diagnosing subtle integration and configuration faults.

Core Features & Use Cases

  • Cross-file / cross-stack checks: Grep and glob-based scans combined with referential checks against project reference documents to verify APIs, topics, and config keys.
  • Targeted rule catalog: Applies a comprehensive catalog of checks (YAML/JSON formatting, PromQL/LogQL pitfalls, Docker compose keys, Grafana panel structure, Python async/import patterns, ESP32 constraints) and maps findings to severity and remediation.
  • Structured audit reporting: Produces a standardized Markdown report with context, references used, categorized findings by ID, and prioritized recommendations. Use case: audit Grafana dashboards and Docker compose files for hallucinated settings and threshold logic before deploying monitoring to production.

Quick Start

Request an audit for the Grafana dashboards and Docker compose files to identify AI-generated configuration and logic errors.

Frequently Asked Questions about ki-audit

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

FAQPage Schema
How do I find AI-generated configuration and logic errors in Docker and Grafana files?

Detecting AI-generated configuration errors in Docker and Grafana involves cross-referencing files against project documents to uncover hallucinated settings and semantic logic faults. The audit applies targeted grep and glob inspections, outputting a structured Markdown report with categorized findings, severity ratings, and remediation steps.

What are common AI-induced syntax and mapping issues in FastAPI code?

AI-induced issues in FastAPI code often include hallucinated APIs, outdated syntax, incorrect async import patterns, and semantic logic errors. A targeted code audit cross-references Python files against project reference documents to pinpoint these syntactically valid but semantically incorrect mappings, generating a structured report with prioritized remediation steps.

Can I audit ESP32 snippets for hallucinated APIs and version mismatches?

Yes, you can audit ESP32 snippets for hallucinated APIs and version mismatches. The audit process applies a targeted rule catalog to verify ESP32 constraints and cross-references project files to identify incorrect mappings, ultimately delivering a structured Markdown report with findings, severity levels, and remediation guidance.

Does this code audit tool work with Docker Compose and PromQL configurations?

Yes, this code audit tool works with Docker Compose and PromQL configurations by applying a targeted rule catalog to verify keys, formatting, and query pitfalls. It cross-references your infrastructure files to detect hallucinated settings and threshold logic errors before production deployment, generating a structured Markdown audit report with prioritized recommendations.

What is the best way to check for incorrect nesting in Grafana dashboard panels?

The best way to check for incorrect nesting and structural faults in Grafana dashboard panels is to perform a targeted audit using glob and grep scans. This process maps findings to severity levels by cross-referencing panel structures against project reference documents, yielding a structured Markdown report with categorized findings and remediation guidance.