1c-dev: repository-infobase-XML round trip for 1C
1c-dev — Claude Code skill for 1C:Enterprise development
A Claude Code plugin that drives the 1C configuration repository round trip: update, dump to XML, lock objects, edit, load back, commit
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Runs 1cv8.exe DESIGNER, which can change the working infobase configuration
- Commits changes to the shared configuration repository on the user's behalf
- Infobase and repository passwords are stored in plain text in 1c-project.json
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/1c-dev-claude-code-skill-for-1c-enterprise-developmentDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add sabissimo/1c_developer_skill
/plugin install 1c-dev@1c-developer-skillInstall the plugin with /plugin marketplace add Sabissimo/1C_Developer_Skill and /plugin install 1c-dev@1c-developer-skill in Claude Code, restart the session, open the 1C project folder and tell the agent: this is a 1C project, set it up.
Other ways from the author
/plugin marketplace add Sabissimo/1C_Developer_Skill
/plugin install 1c-dev@1c-developer-skillThe recommended method from the README. Update later with /plugin marketplace update 1c-developer-skill.
This is third-party code. Review the repository files before installing.
What it does
The skill automates the 1C configuration repository routine on a dedicated server development infobase. On command, it checks the repository for new versions and pulls them, keeps an incremental XML dump of the configuration, locks objects before editing and stops if someone else holds them, and after Claude edits the sources it loads back only the changed files, updates the infobase configuration and commits to the repository with a task comment. All steps are driven by PowerShell or Bash scripts that run 1cv8.exe DESIGNER in batch mode and parse its logs, because the designer sometimes exits with code 0 even on failure.
Who it is for. For 1C developers who want Claude Code to manage the repository-infobase-XML cycle itself instead of manual exports through the Configurator.
Good fit when
- Development happens on a server infobase bound to a configuration repository
- You want the agent to lock objects, edit XML and commit to the repository on its own
- You need unchanged files left untouched during XML dumps
Not a fit when
- You use a file-based infobase: the README explicitly excludes this from v1
- You develop in EDT or through configuration extensions: also out of scope for v1
- You need to work with several repositories at once
Example request
This is a 1C project, set it up and update the configuration from the repository before I start workingLimitations
It needs Windows, 1C:Enterprise 8.3.11 or newer under Program Files\1cv8, and a dedicated server infobase for development with no data and no other users. Passwords are stored in plain text in 1c-project.json; the skill adds the file to .gitignore automatically, but it still needs care. File-based infobases, configuration extensions, EDT projects and multi-repository setups are out of scope for v1. The full cycle was verified live on platform 8.3.19.1351; for other builds the README asks to re-check against its checklist.
How to disable. Remove the plugin with /plugin marketplace remove 1c-developer-skill in Claude Code, or delete the ~/.claude/skills/1c-dev folder if installed manually.
Security check
- Runs 1cv8.exe DESIGNER, which can change the working infobase configuration
- Commits changes to the shared configuration repository on the user's behalf
- Infobase and repository passwords are stored in plain text in 1c-project.json
README in short
The README describes the repository-infobase-XML automation, platform and infobase requirements, two install paths (Claude Code plugin or manual skill copy), the list of files the skill creates in a project and which should be git-ignored. It lists bash and PowerShell test commands and the v1 limitations. License is MIT.
SKILL.md
--- name: 1c-dev description: >- 1C:Enterprise development workflow automation. Use when a project involves 1C configuration development: editing configuration XML/BSL sources, syncing with a 1C configuration repository (хранилище конфигурации), updating an infobase from the repository, locking/committing objects, or loading XML changes back into the configuration. Triggers: "1C", "1С", "конфигурация", "хранилище", "конфигуратор", "BSL", "1cv8". --- # 1C Developer Skill Automates the 1C configuration-repository round-trip for server infobases: update from хранилище -> dump to XML -> lock objects -> edit -> partial load back -> commit. All heavy lifting is done by scripts driving 1cv8.exe DESIGNER in batch mode.
FAQ
What happens if two people hold the same object?
The skill hard-stops on the lock conflict (exit code 3) instead of continuing.
Can I install the skill manually, without the plugin?
Yes, option B: clone the repo and run install.ps1 or install.sh, which copy skills/1c-dev into ~/.claude/skills/1c-dev.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything