sync-providers

Analyze provider interfaces and sync Fake/Real implementations with generated stubs.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dezverev/AnimalAL-v1 --skill sync-providers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-providers
Source: https://github.com/dezverev/AnimalAL-v1/tree/main/.cursor/skills/sync-providers
Command: npx skills add https://github.com/dezverev/AnimalAL-v1 --skill sync-providers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures Real and Fake provider implementations stay in sync with their interfaces, preventing drift between code and tests and improving reliability of the provider layer.

Core Features & Use Cases

  • Scan provider interfaces and their Fake/Real implementations to detect missing methods, method mismatches, and data inconsistencies.
  • Validate fake data against real provider patterns and suggest or auto-generate stubs for testing.
  • Apply fixes after interface changes or when adding new provider methods to keep all implementations aligned.
  • Use after refactoring to maintain consistency across the provider surface.

Quick Start

Run the provider-sync workflow by issuing /sync-providers or "sync providers" to check alignment, and use /sync-providers --fix to auto-generate missing Fake methods.

Frequently Asked Questions about sync-providers

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

FAQPage Schema
How do I keep fake and real provider implementations in sync with their interfaces?

To keep fake and real provider implementations in sync, this skill analyzes provider interfaces to detect missing methods, mismatches, and data inconsistencies, then applies fixes or generates safe stubs automatically.

What is the best way to auto-generate missing fake provider methods after a refactor?

The best way to auto-generate missing fake provider methods is running the provider-sync workflow with the --fix flag, which safely creates stubs to maintain consistency across the provider surface.

Does this provider sync workflow target a specific project directory structure?

Yes, the provider sync workflow specifically targets the src/Plugins/Providers path and follows AnimalAI project conventions for in-memory validation and safe, auto-generated stubs.

Why do my fake provider tests fail with method mismatches after interface updates?

Fake provider tests fail with method mismatches because real and fake implementations drift from updated interfaces; scanning provider interfaces detects these inconsistencies and suggests fixes to realign them.

Can I validate fake data against real provider patterns automatically?

Yes, you can validate fake data against real provider patterns automatically by scanning provider interfaces and implementations, allowing the system to suggest or auto-generate accurate stubs for testing.