Orchestrate end-to-end 1C Configuration Extension workflows from scaffold to validation.
npx skills add https://github.com/msrv-tech/skills --skill cfe-full-cycle
Please help me install this Agent Skill. Skill: cfe-full-cycle Source: https://github.com/msrv-tech/skills/tree/main/cfe-full-cycle Command: npx skills add https://github.com/msrv-tech/skills --skill cfe-full-cycle
Coordinating end-to-end 1C Configuration Extensions (CFE) development activities across multiple steps is error-prone and time-consuming.
Run the sequence cf-info → cfe-init → cfe-borrow → cfe-patch-method → meta-compile → form-add → form-compile → cfe-validate with the target configuration.
High-intent search queries and answers about installing and using this skill.
To orchestrate a 1C Configuration Extension workflow, you run a specific sequence: cf-info, cfe-init, cfe-borrow, cfe-patch-method, meta-compile, form-add, form-compile, and cfe-validate. This coordinates steps to deliver a validated CFE package.
The process for borrowing objects and patching methods in 1C CFE development involves using the cfe-borrow and cfe-patch-method steps within the extension workflow. This allows method interception and modification before final form assembly and validation.
Yes, this CFE creation workflow works across various ERP deployments and development environments. It coordinates scaffold generation, object borrowing, and form assembly to ensure compatibility and deliver a ready-to-use extension package.
To assemble and compile forms during 1C Configuration Extension creation, you use the form-add and form-compile steps. These follow meta-compile and precede cfe-validate in the orchestrated workflow sequence to finalize the extension.
1C extension validation can fail if the workflow sequence is not properly coordinated. Ensure you execute cf-info, cfe-init, cfe-borrow, cfe-patch-method, meta-compile, form-add, form-compile, and cfe-validate in exact order to ensure compatibility.
Yes, you need to run meta-compile before adding forms in a 1C CFE workflow. The required sequence is cf-info, cfe-init, cfe-borrow, cfe-patch-method, meta-compile, form-add, form-compile, and cfe-validate to produce a validated extension.
Desko77Orchestrate 1C CFE extension workflows from scaffold to validation.
KrismithReddy12Merge pull requests, trigger CI/CD pipelines, and validate production health.
msrv-techGenerate method interceptor skeletons for 1C extensions and write decorated methods into .bsl files.
Alex1980AlexAutomate 1C task implementation from ANALYSIS-REPORT.md with SQL validation and BSL changes.
