compilation-validator

Validate Fakt-generated fake code for compile errors across Kotlin Multiplatform and JVM targets.

63|6|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/rsicarelli/fakt --skill compilation-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compilation-validator
Source: https://github.com/rsicarelli/fakt/tree/main/.claude/skills/validation/compilation-validator
Command: npx skills add https://github.com/rsicarelli/fakt --skill compilation-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that Fakt-generated fake code compiles without errors, ensuring proper type safety and a properly typed DSL, with zero TODO blockers (Phase 1).

Core Features & Use Cases

  • Scope-based validation: validate specific interface or all generated fakes
  • Build orchestration: runs Gradle builds across platforms to verify compatibility
  • Output verification: checks generated files exist and types align with interfaces

Quick Start

Run the validator with a scope (e.g., --all or --interface=AsyncService) and review the compilation report to confirm success or diagnose issues.

Frequently Asked Questions about compilation-validator

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

FAQPage Schema
How do I validate that Fakt-generated fake code compiles without errors?

Run the compilation validator with a scope flag (--all for all fakes or --interface=YourInterface for a specific interface) to trigger code generation, execute Gradle builds across your Kotlin Multiplatform and JVM targets, and receive a detailed compilation report confirming success or diagnosing issues.

Can I validate Fakt fake code on both Kotlin Multiplatform and JVM targets?

Yes, the validator orchestrates Gradle builds across Kotlin Multiplatform and JVM targets simultaneously, ensuring your generated fakes compile cleanly and maintain type safety on both platforms.

What does the compilation validator check in generated fake code?

The validator verifies generated files exist (Fake{Interface}Impl, fake{Interface}, Fake{Interface}Config), ensures type safety for methods, properties, and suspend functions, and enforces zero TODO blockers across all generated fakes or a scoped interface.

How do I debug compilation failures in Fakt-generated fakes?

Run the validator with verbose output and interface-scoped checks to pinpoint which generated fake is failing, then review the detailed compilation report to diagnose type mismatches or structural artifacts.

Does the validator support checking individual interfaces or only all fakes at once?

The validator supports both scope-based validation: check all generated fakes with --all or validate a specific interface (e.g., --interface=AsyncService) to isolate and verify individual fake implementations.

What happens if TODO blockers are found in generated fake code?

The validator enforces zero TODO blockers as part of Phase 1 validation; any TODOs in generated code will be flagged in the compilation report, indicating incomplete or unresolved fake implementations that must be addressed.