plugin-api-change

Safely implement or modify a Unity plugin API in the AppsFlyer Unity plugin, including C# API, Android Java bridge, and iOS Objective-C bridge changes.

Ir para a instalação

Repositório: AppsFlyerSDK/appsflyer-unity-plugin
Última atividade na origem: 17 de maio de 2026 às 09:52
Idioma detectado do SKILL.md: inglês
Estrelas: 177
Forks: 67

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/AppsFlyerSDK/appsflyer-unity-plugin --skill plugin-api-change

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

sdk-version-bump

Safely bump the wrapped Android SDK or iOS SDK version in the AppsFlyer Unity plugin, update the plugin version if needed, and validate all related files including both billing library variants.

2026-06-04

appsflyer-event-validation

Validate that expected AppsFlyer SDK events and callbacks were triggered during an end-to-end Unity app scenario using logs, callback payloads, and test evidence.

2026-05-17

e2e-smoke-test

Run or review a basic end-to-end smoke test for the AppsFlyer Unity plugin on Android emulator or iOS simulator, covering startup, initialization, and basic event flow.

2026-05-17

Ver todas deste repositório

Plugin API Change

Use this skill when adding, removing, or changing a Unity plugin API.

Goal

Make a safe API change across all plugin layers while preserving backward compatibility where possible.

Workflow

Identify the public C# API being changed in Assets/AppsFlyer/AppsFlyer.cs.

Trace the full path: C# API → AppsFlyerAndroid.cs (Android) | AppsFlyeriOS.cs (iOS) → Native bridge

Verify whether the API already exists in some form.

Check whether the change affects: method signatures, argument mapping, callback behavior, event payload shape, Android/iOS parity.

Implement changes in all required layers.

Check whether tests or example code must be updated.

Summarize compatibility risk and missing validation.

What to Check

C# layer

AppsFlyer.cs — public API entry point

AppsFlyerAndroid.cs — Android delegation (uses AndroidJavaClass/AndroidJavaObject)

AppsFlyeriOS.cs — iOS delegation (uses [DllImport("__Internal")])

#if UNITY_IOS / #if UNITY_ANDROID guards

Assembly definition (.asmdef) boundaries — do not break

Namespace AppsFlyerSDK — do not change

Android bridge

AppsFlyerAndroidWrapper.java — Java bridge method

Mapping to AppsFlyer Android SDK

Threading safety

iOS bridge

AppsFlyeriOSWrapper.mm — Objective-C++ bridge function

Mapping to AppsFlyer iOS SDK

Delegate/callback wiring

Output Format

Return:

Summary

C# API impact

Android impact

iOS impact

Assembly definition impact

Compatibility risk

Tests to add or update

Validation steps

Rules

Keep Android and iOS behavior aligned unless a platform difference is intentional.

Do not silently break the public C# API.

Both billing library variants must remain buildable after the change.

Do not stop at C#-only changes if native bridge work is required.

name	plugin-api-change
description	Safely implement or modify a Unity plugin API in the AppsFlyer Unity plugin, including C# API, Android Java bridge, and iOS Objective-C bridge changes.