cf-add-object

Automate metadata object addition into a 1C configuration with validation.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill cf-add-object
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-add-object
Source: https://github.com/msrv-tech/skills/tree/main/cf-add-object
Command: npx skills add https://github.com/msrv-tech/skills --skill cf-add-object

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end addition of a metadata object into a 1C configuration, orchestrating meta-compile, cf-edit, subsystem-edit, form-add, form-compile, and validate steps.

Core Features & Use Cases

  • Orchestrates the full workflow to add a new object across configuration, subsystem linkage, and validation.
  • Ensures the object is correctly created, added to Configuration.xml, and wired into the appropriate subsystem.
  • Use Case: Quickly add a Catalog or Document with required attributes and have the system validate integrity.

Quick Start

Invoke the skill with the object type and name and the target configuration path to initiate the full add-object workflow.

Frequently Asked Questions about cf-add-object

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

FAQPage Schema
How do I add a new metadata object to a 1C configuration from source folders?

To add a metadata object to a 1C configuration, you need an automated workflow that creates the object, updates Configuration.xml, links it to the target subsystem, compiles forms, and runs validation checks end-to-end.

What does end-to-end metadata object creation in 1C involve?

End-to-end object creation in 1C involves orchestrating meta-compile, cf-edit, subsystem-edit, form-add, form-compile, and validation steps to ensure the new object is correctly integrated and structurally sound.

Can I use this workflow to add a Catalog or Document with required attributes in 1C?

Yes, you can use this workflow to quickly add a Catalog or Document in 1C with required attributes, automatically wiring it into the appropriate subsystem and validating configuration integrity.

Do I need to manually edit Configuration.xml when adding a new object to a 1C subsystem?

No, you do not need to manually edit Configuration.xml when adding an object to a 1C subsystem; the automated process correctly creates the object, adds it to the configuration file, and wires it into the subsystem.

How do I validate a new 1C configuration object after adding it to source code folders?

Validating a new 1C configuration object is handled by the same end-to-end workflow that adds it, running built-in validation steps to confirm structural integrity and proper subsystem linkage after creation.