sync-providers-claude

Analyze provider interfaces and synchronize Fake and Real implementations with their contracts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures Real and Fake provider implementations stay in sync with their interfaces, automatically identifying missing or mismatched methods, validating fake data consistency, and suggesting realistic stubs to align patterns across the codebase.

Core Features & Use Cases

  • Interface-driven synchronization: scans Interfaces and corresponding Fake/Real implementations.
  • Auto-generation of missing stubs: creates compile-ready Fake methods to close gaps.
  • Consistency validation: checks method signatures, return types, and naming conventions to ensure alignment.

Quick Start

Run: /sync-providers to validate all providers, or /sync-providers --fix to auto-generate missing stubs and apply fixes.

Frequently Asked Questions about sync-providers-claude

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 in .NET?

Provider interface synchronization scans interface files and corresponding Fake/Real implementations to report mismatches and auto-generate missing stubs. It parses public methods returning Task or Task<T>, validating naming and type conventions.

What's the best way to auto-generate missing Fake provider stubs from existing interfaces?

Auto-generating missing Fake stubs uses the --fix command to create compile-ready methods that close implementation gaps. This ensures Fake and Real providers align perfectly with their defined contracts.

Why does my Fake provider implementation have mismatched method signatures with the Real provider?

Mismatched method signatures occur when Fake and Real implementations diverge from the interface contract. Synchronization validation checks method signatures, return types, and naming conventions to identify and report these inconsistencies.

Can I validate provider interface conventions for Task and Task<T> return types without external I/O?

Yes, interface convention validation parses public methods returning Task or Task<T> and outputs actionable guidance without performing external I/O. It enforces naming and type conventions across all scanned provider implementations.

Does interface-driven synchronization work with my existing codebase under src/Plugins/Providers/Interfaces?

Interface-driven synchronization scans interface files located under src/Plugins/Providers/Interfaces and their corresponding Fake and Real implementations. It requires no external dependencies to analyze and validate provider contracts.

How do I check for missing or mismatched methods across provider interfaces and implementations?

Checking for missing or mismatched methods involves scanning provider interfaces and comparing them against Fake and Real implementations. The validation reports gaps and can suggest realistic stubs to align patterns across the codebase.