companion-add-action-to-category-file

Open the existing src/actions/action-{category}.ts file, add a new member to the action enum with a globally unique string ID, then append a matching entry in the actions object inside the GetActions function. The aggregator file does not need any changes.

Use a sync callback with signature (): void when the action performs no awaits and parses no options. Use an async callback returning Promise<void> when you need await, such as calling instance.parseVariablesInString on user-provided option values.

This skill extends an existing action category file only. Use companion-action-file-pattern when no src/actions/action-{category}.ts file exists yet, since it creates the new file and wires it into the actions.ts aggregator.

The enum string value is the action ID registered with Companion and must be globally unique across all category enums in the module. Check the other action enums and rename the conflicting string value.

Option values from the action event are loosely typed, so you must cast them explicitly, for example action.options.userName as string. Also ensure the option id in the definition matches the property you access.