👯 AdMob API Parity Checker

SkillDev tools

Ensure API parity between GDScript and C#. Use when adding new methods, signals, or features to the plugin bridge to verify that Mono users have identical functionality.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the 👯 AdMob API Parity Checker skill

What this skill tells your AI

The instructions your AI receives, as published by poingstudios/godot-admob-plugin in .agents/skills/parity-checker/SKILL.md and read by ahel’s review.

Ensure that GDScript and C# implementations remain synchronized and consistent.

⚖️ The Parity Standard

1. Method Naming

  • GDScript: snake_case (e.g., load_ad)
  • C#: PascalCase (e.g., LoadAd)
  • Note: Internal _plugin.Call("method_name") must always use the EXACT string defined in the native bridge (usually snake_case).

2. Implementation Check

For every new feature in admob.gd:

  • Create/Update the corresponding .cs class in csharp/src/Api/.
  • Ensure SafeConnect is used for signals in C#.
  • Verify that all optional parameters have the same default values in both languages.

3. Sample Sync

  • If a feature is added to gdscript/sample/Main.gd, it MUST be added to csharp/sample/MainCSharpExample.cs.
  • Verify that the C# sample actually instantiates the classes (to trigger Static Initializers/Warnings).

🛠️ Verification Command

  • Run grep -r "_get_plugin" . and grep -r "GetPlugin" . to compare list of initialized modules.

Signals

GitHub stars
616
Forks
50
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
parity-checker
Source
github.com/poingstudios/godot-admob-plugin