1c-codex-skills: Claude hands 1C tests and review to Codex CLI
1c-codex-skills
Four Claude Code skills: 1C testing through Codex and 1c-testpilot, code review, export and load through ibcmd
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Runners launch Codex CLI as a separate process, and the 1C test client runs scenarios in your database
- `ibcmd-1c` loads data into the infobase and updates the database configuration
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/1c-codex-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runners launch Codex CLI as a separate process, and the 1C test client runs scenarios in your database
- `ibcmd-1c` loads data into the infobase and updates the database configuration
This is third-party code. Review the repository files before installing.
What it does
The set of four skills follows the principle "Codex executes, Claude verifies". `codex-test-1c` launches Codex CLI, which runs scenarios in a 1C test client through the `1c-testpilot` MCP server and writes a report. `codex-review-1c` asks Codex to read edits and return findings by severity, and the mode is chosen automatically: objects of a 1C:EDT project or a Configurator export without git. Claude confirms Codex findings against code, metadata or data. `ibcmd-1c` loads and exports data through `ibcmd` without the Configurator: partial and full import from XML, a database export, creating a database from `.dt` or `.cf`, a `.cf` and `.cfe` backup. `1c-mcp-toolkit-gotchas` collects typical failures when working with `1c-mcp-toolkit`. The result of every run is appended to the project memory.
Who it is for. 1C developers and testers on Windows who work in Claude Code and want to bring Codex in as a second executor.
Good fit when
- Functional scenarios in a 1C test client must run automatically with a report
- Edits in an EDT project need a code review with findings verified against code
- Configuration sources are exported or loaded into a database in batches without the Configurator
- After a client restart the `1c-mcp-toolkit` connection dropped and you need a checklist of causes
Not a fit when
- Linux and macOS: runners are written in PowerShell 5.1 and target Windows
- No Codex CLI: testing and review are built on it, while `ibcmd-1c` and `1c-mcp-toolkit-gotchas` work without Codex
- You need testing without a 1C client license: the test client requires 8.3.27 or newer, or 8.5.1
Example request
Test the "Sale" document posting scenario with Codex using the prompt from docs/test.md and show the reportLimitations
It needs Windows, PowerShell 5.1 and Codex CLI, and the author checked versions 0.155 and 0.160. Testing adds a 1C platform 8.3.27 or newer with a license and the `1c-testpilot` MCP server with an `.env` file. A Codex update can erase the MCP section in `config.toml`, and the runner catches it. A full run takes 20–60 minutes as a separate process. The repository has no license file. One author, the last commit in November 2026, no stars.
How to disable. Delete the skill folders from `%USERPROFILE%\.claude\skills\` and the `[mcp_servers.1c-testpilot]` section from `%USERPROFILE%\.codex\config.toml`.
FAQ
How do I invoke the skills?
With `/codex-test-1c <prompt.md>`, `/codex-review-1c <path or file>` and `/ibcmd-1c load|export`. The `1c-mcp-toolkit-gotchas` skill turns on by itself when 1C MCP tools are in use.
How do I check the Codex link to 1C?
Run `run-codex-test.ps1` with the `-Probe` flag: within a minute `last_message.md` shows a `list_profiles` reply with `ok: true`.
How does the edt mode differ from offline?
In edt mode Codex reads objects directly in a 1C:EDT project by tree paths. In offline mode a Configurator export works without git, with a file copy and diffs.
What does EXIT 0 with TESTPILOT_CALLS 0 mean?
Codex finished but never reached 1C: there were no `tc_*` tool calls. Causes are listed in `TROUBLESHOOTING.md`.
Is Codex needed for `ibcmd-1c`?
No. The `ibcmd-1c` skill and the `1c-mcp-toolkit-gotchas` skill work without Codex, and `ibcmd` needs 1C platform 8.3.14 or newer.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA 1C development skill collection for Codex and Claude Code: XML sources, forms, data composition, infobases, web publishing and an HTTP test bridge
A large set of skills, rules and commands that let an agent build and parse 1C sources in the platform's format, without the Designer
Skills covering the full 1C:Enterprise 8.3 development cycle, from XML sources to publishing and web client testing
A skill and tester agent for Claude Code that test the 1C interface through the 1c-testpilot MCP server with evidence
Tester
Тестер
A scenario testing system for 1C:Enterprise with a set of agent skills that let an AI agent operate the application like a regular user
A Copier project template for 1C with a bundle of SKILL.md files for Claude Code and Codex: dump, load, tests and extension builds via stable scripts
README in short
Describes four skills, requirements, installation by copying folders, MCP setup for Codex and Claude, the test run order, review modes and typical pitfalls.
README badge
Original SKILL.md
--- name: codex-test-1c description: Функциональное тестирование доработок 1С силами Codex через MCP 1c-testpilot (Codex сам управляет тест-клиентом 1С в фоне, Claude потом разбирает отчет и проверяет находки по коду). Используй когда просят «протестировать кодексом», «отдать тесты Codex», прогнать промт тестирования в базе без участия пользователя. argument-hint: <промт_тестирования.md> [--model <модель>] [--effort low|medium|high|max] allowed-tools: - Bash - PowerShell - Read - Write - Edit - Monitor --- # /codex-test-1c — тестирование 1С силами Codex + 1c-testpilot Codex (`codex exec`) получает промт тестирования, сам запускает тест-клиент 1С через MCP-сервер `1c-testpilot`, проходит сценарии и пишет отчет. Claude запускает Codex, ждет завершения, разбирает отчет, **проверяет каждую находку по коду** и исправляет дефекты. Ниже `<SKILL_DIR>` — каталог этого скилла (там лежит `scripts/`). ## Предусловия (проверить ДО запуска) 1. Пользователь загрузил в базу актуальную версию расширения/конфигурации. Не выяснено — спросить. 2. Нет «висящих» тест-клиентов на этой базе: `Get-CimInstance Win32_Process -Filter "Name='1cv8.exe' or Name='1cv8c.exe'"`, ищем `/TESTCLIENT`. Процессы пользователя (Конфигуратор, его сеансы) НЕ убивать — только сообщить. 3. Промт тестирования (`.md`) самодостаточен: база, пользователь, версия платформы, сценарии с ожидаемым результатом, **путь файла отчета**, куда класть скриншоты и тестовые файлы. Если в базе нет данных для сценария (пустые справочники и т. п.), в промте описан обход: копирование существующих документов. Шаблон — `examples/prompt-template.md` в репозитории. 4. Отчет предыдущего прогона не должен перезаписываться: у нового файла отчета свой суффикс (`_повтор`, `_2`…). 5. В `~/.codex/config.toml` есть секция `[mcp_servers.1c-testpilot]` (раннер проверяет сам: `PREFLIGHT FAIL` в `status.txt`). Обновление Codex может ее стереть — вернуть так (пути прямыми слэшами, чтобы не мучиться с экранированием): ```toml [mcp_servers.1c-testpilot] command = "C:/Users/<user>/.local/bin/1c-testpilot.exe" args = ["--env-file", "<путь к каталогу testpilot>/.env"] startup_timeout_sec = 60 ``` Это постоянная правка конфига пользователя — с его согласия и с копией `config.toml.bak_<дата>`. 6. В промте `launch_client` вызывается с **`exe` и `version` той платформы, на которую есть лицензия** (например `exe="C:\Program Files\1cv8\<версия>\bin\1cv8c.exe", version="<версия>"`). Без них testpilot берет `TC1C_PLATFORM_EXE` из своего `.env` — если на ту версию нет лицензии, появится окно «Лицензия не обнаружена», прогон стоит. 7. В промте НЕ запрещать «JavaScript / `tools.*`» — это и есть рабочий путь вызова MCP (см. ниже).