skills.rest
yellow-hammer
yellow-hammerOFFICIAL
Explore all skills by this author →
GitHub

1c-platform-tools-setversion

Set configuration versions for 1C projects via MCP or extension command.

178|16|Updated Dec 9, 2025
Search Tags:#configuration#mcp#command#project-setup#set-version#1c-platform-tools#vanessa
One-click install
npx skills add https://github.com/yellow-hammer/vscode-1c-platform-tools --skill 1c-platform-tools-setversion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 1c-platform-tools-setversion
Source: https://github.com/yellow-hammer/vscode-1c-platform-tools/tree/main/resources/skills/1c-platform-tools-setversion
Command: npx skills add https://github.com/yellow-hammer/vscode-1c-platform-tools --skill 1c-platform-tools-setversion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

1C projects often require updating configuration versions, ConfigDumpInfo, or metadata manually, which is error-prone and repetitive. This Skill automates and centralizes the versioning workflow.

Core Features & Use Cases

  • Set configuration version via the 1C Platform Tools extension command or MCP.
  • Update version information in ConfigDumpInfo or in metadata across a project.
  • Accept a mandatory projectPath pointing to the 1C project root (defaults to workspace root if not provided) and work with both existing and new projects.

Quick Start

Run the 1C Platform Tools setVersion.configuration command on the target project to apply the desired version.

Frequently Asked Questions about 1c-platform-tools-setversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set the configuration version for a 1C project automatically?▼

Set the 1C configuration version by running the 1c-platform-tools setVersion.configuration command with a mandatory projectPath parameter to update version metadata and ConfigDumpInfo automatically.

What is the best way to update ConfigDumpInfo across 1C projects?▼

Updating ConfigDumpInfo across 1C projects is best handled by using this MCP extension command, which centralizes the versioning workflow and applies version metadata changes automatically to prevent repetitive manual errors.

Do I need a packagedef file to apply version updates to 1C project metadata?▼

Yes, applying version updates requires a project root containing the packagedef file. The command uses the mandatory projectPath parameter to locate the 1C project root and apply the configuration version changes correctly.

Can I use MCP to set the configuration version for a new 1C project?▼

Yes, you can use MCP to set the configuration version for both existing and new 1C projects. The command requires the projectPath parameter pointing to the 1C project root, defaulting to the workspace root if not provided.

Why does manually updating 1C project version metadata lead to errors?▼

Manually updating 1C project version metadata leads to errors because the process is repetitive and error-prone. Automating the versioning workflow via the setVersion.configuration command centralizes updates and ensures consistent metadata changes.

Related Skills

Explore More Software Engineering Skills→
yellow-hammeryellow-hammer
178

1c-platform-tools-external

Build and decompile 1C EPF/ERF external objects via extension commands or MCP tools.

Official
Intermediate
ChoshimWyChoshimWy
8

xcode-build

Configure Xcode build settings, signing, and CI/CD workflows.

Community
Advanced
yellow-hammeryellow-hammer
178

1c-platform-tools-run

Launch 1C: Designer and Enterprise for a given project path.

Official
Intermediate
Alex1980AlexAlex1980Alex

help-add

Generates a complete help package for 1C objects with a single command.

Community
Intermediate