erf-build

Compile 1C XML report sources into deployable ERF binaries.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill erf-build-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: erf-build
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/erf-build
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill erf-build-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the tedious process of compiling 1C external report (ERF) binaries from XML source files, so you can reliably generate a deployable ERF without manual setup.

Core Features & Use Cases

  • ERF Compilation: Builds a target ERF file from the root XML of a report by providing the report name.
  • Flexible Source/Output Paths: Uses configurable source directory (default src) and output directory (default build) to fit your project layout.
  • Robust Database Connectivity Strategy: Prefers an existing database by reading .v8-project.json and Git branch-to-database mapping, but falls back to a temporary base with metadata stubs when connection details are missing or not resolvable.

Quick Start

Request: Ask the AI to run erf-build for report "MyReport" to compile it from src into build.

Frequently Asked Questions about erf-build

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

FAQPage Schema
How do I compile a 1C ERF report from XML source files?

To compile a 1C ERF report, you can build the deployable external report binary from its root XML by providing the report name, allowing the system to automatically resolve paths and produce the output file.

What is the best way to automate 1C external report generation?

Automating 1C external report generation involves invoking a shared compilation script that reads XML sources and builds the ERF binary, eliminating the need for manual setup and compilation steps.

Do I need a configured 1C database to build an ERF file?

You do not need a manually configured 1C database to build an ERF file; the build process can fall back to using a temporary base with stub metadata when existing connection details are missing or unresolvable.

How does the ERF build process find the correct source and output directories?

The ERF build process finds directories by using configurable source and output paths, defaulting to src and build respectively, while reading .v8-project.json to resolve the v8path and select the database.

Can I use a temporary base with stub metadata for 1C ERF compilation?

Yes, you can use a temporary base with stub metadata for 1C ERF compilation, which serves as a robust fallback when Git branch-to-database mapping cannot resolve an existing database connection.