1c-platform-tools-support

To automate 1C platform packaging, you can use extension commands or MCP-based operations to export distributed files and assemble distributive packages. The process resolves the project root to a working directory and validates inputs before executing actions deterministically.

Updating cf and cfu configurations is handled through dedicated extension commands that synchronize support settings for your 1C project. The workflow validates the project path and applies deterministic execution patterns to ensure accurate configuration updates.

Yes, you can use MCP tooling to create delivery templates and distribution files when available. The MCP operations utilize a projectPath abstraction to perform the same packaging and support tasks as direct extension commands.

Removing support from cf/cfu files is executed via specific extension commands designed for 1C platform projects. The system validates inputs and resolves the project root before performing the support removal action deterministically.

Yes, 1C platform packaging automation works without additional dependencies. The Skill operates through direct extension commands or MCP-based operations, requiring only a valid project root directory and proper input validation to execute distribution workflows.