feat: add extension-to-functions-codebase migration skill#143
feat: add extension-to-functions-codebase migration skill#143shettyvarun268 wants to merge 3 commits into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new skill and reference guides for migrating Firebase Extensions to standalone Cloud Functions for Firebase (CF3) codebases, detailing V1 to V2 trigger upgrades. The feedback highlights several areas for improvement: correcting invalid destructuring syntax in the main skill file, fixing malformed markdown backticks in the configuration migration guide, using correct camelCase parameter variables for secret binding examples, and standardizing the V2 function names in the signature mapping reference to use direct imports rather than namespaced ones.
| | V1 Trigger | V2 Equivalent | Shimmed Key | Destructuring Pattern | | ||
| | :--- | :--- | :--- | :--- | | ||
| | `pubsub.topic().onPublish()` | `onMessagePublished()` | `message` | `({ message, context })` | | ||
| | `pubsub.schedule().onRun()` | `scheduler.onSchedule()` | **N/A** | Access `event` directly | |
There was a problem hiding this comment.
For consistency with the other direct imports listed in the table (such as onDocumentWritten() and onMessagePublished()), the V2 equivalent for scheduled functions should be listed as onSchedule() instead of scheduler.onSchedule().
1 participant
This pull request introduces the extension-to-functions-codebase agent skill, designed to guide AI coding assistants through migrating installed Firebase Extensions to standalone Cloud Functions (CF3). It enables fully automated deployments by parsing permission and API requirements from extension.yaml and declaring them directly in code via the new requiresRole() and requiresAPI() SDK methods, completely removing the need for manual service account setup. It also automates the transition of lifecycle events using native SDK hooks (afterInstall/afterUpdate).
To ensure long-term compatibility, the skill instructs the agent to modernize any legacy Functions V1 triggers to V2 using the SDK's destructuring compatibility shim. This shim preserves the existing function bodies, so internal business logic requires no rewriting. The skill also incorporates best practices such as safe git copy sequences, parameterization mappings, and using onInit() for global variable initializations to prevent runtime crashes. Technical reference tables mapping triggers, options, and parameters have been included in a dedicated references/ directory.