1c-quality-gate

A Claude Code and OpenCode plugin that will not let a session end until 1C edits pass standards, architecture and XML checks

PluginMedium riskRussian stack

romandredan/1c-quality-gate

Install

/plugin marketplace add Romandredan/1c-quality-gate
/plugin install 1c-quality-gate

Restart the session after install, /gate-status should report that the gate is not armed.

This is third-party code. Review the repository files before installing.

What it does

Editing a .bsl file or metadata XML arms a gate: in Claude Code a Stop hook blocks the session from ending until the check runs, and in OpenCode the plugin keeps pulling the agent back to unchecked files. Depth is computed from edit volume, code archetypes and complexity, so a comment fix passes quickly while a transaction or new common module gets a full review. Review loops check code against 1C standards and a static analyzer, architecture against SOLID and GRASP, metadata XML and file hygiene. The output is a findings report plus a machine-readable trail of what was checked, what was skipped and why.

Who it is for. For 1C developers who edit configuration or extension dumps as files together with Claude Code or OpenCode.

Good fit when

  • The agent writes BSL and every change must be checked before commit
  • You want a report citing standard numbers and measured values, not general advice
  • You need to catch broken metadata XML after agent edits

Not a fit when

  • Development happens in the Designer without dumping sources to files
  • The project is not 1C: the hooks stay silent there

Example request

/gate run the quality check on my edits to the РасчетСкидок common module

Limitations

It requires HTTP access to the v8std standards MCP service, and the gate cannot be released without it. The static analyzer downloads on the first run. Module compilation is not checked without a local 1C platform, and the trail says so. XML validation needs Python and lxml, some architecture signs need a code index. Skills and reports are in Russian.

How to disable. In Claude Code remove it with /plugin uninstall 1c-quality-gate, in OpenCode delete the plugin line from opencode.json.

Security check

  • Hooks run on every edit and control session end
  • Downloads an analyzer binary on the first run
  • Calls a remote standards MCP service

README in short

The README opens with an example of a blocked session end and a report with findings and a trail. It then covers five reasons checks fail when working with a model and the plugin's answer to each. It describes the four review loops, installation for Claude Code and OpenCode, recommended external tools by role, depth scoring on three axes and false-positive safeguards. MIT license.

FAQ

Can the gate be released without a run?

For small edit classes C0 and C1 yes, with a written reason. C2 and C3 require a full run.

What commands are there?

/gate to run checks, /gate-status for scope, and the --deep, --quick and --fix flags.

Playwright CLI

playwright-cli

Editors’ pick

Microsoft's official Playwright CLI with an agent skill: drive a browser through short commands without heavy MCP schemas

CLIMedium risk13.3K
Editors’ pick

The official MCP server debugger: web UI, automation CLI and terminal UI in one package

CLIMedium risk10.9K
Editors’ pick

SonarSource's official MCP server: quality and security issues, quality gates and code analysis from SonarQube Server and Cloud

MCP serverMedium risk648

Open-source AI agent for pull request review: descriptions, feedback and improvement suggestions on GitHub, GitLab and more

CLIMedium risk13K