v8std standards harness skill
v8std-standards-harness
A skill and validator that stop an agent from silently skipping the v8std 1C development standards check on BSL code
- 11 ★ on the repository
- Last commit
Minimal access
Why this level
- Only reads the standards reference and leaves text evidence lines, does not change configuration code
- In gate mode it can block a commit with zero evidence lines, which is intentional default behavior
Install
- Works in
- Services
Manual install
{ "mcpServers": { "v8std": { "type": "http", "url": "https://ai.v8std.ru/mcp" } } }Added to .mcp.json; for Codex the same URL goes into ~/.codex/config.toml.
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Only reads the standards reference and leaves text evidence lines, does not change configuration code
- In gate mode it can block a commit with zero evidence lines, which is intentional default behavior
This is third-party code. Review the repository files before installing.
What it does
The skill connects to the external v8std standards MCP service and solves one problem: making a skipped check visible instead of silent. A two-way situation map, by metadata object and by code action, points the agent to standard numbers for common cases. When a situation is not on the map, the skill requires at least one v8std_search call per work phase. A sentinel check confirms the standards service is alive and its pointer is current, falling back to an offline cache with an honest skipped mark and reason when it is not. A separate Node validator checks that machine-readable evidence lines were actually left, and can run in lint mode for a one-off pass or gate mode to block a commit that has zero entries.
Who it is for. For 1C developers who let an AI agent touch production BSL code and want verifiable proof that development standards were actually applied, not just mentioned in an instruction.
Good fit when
- An agent writes or reviews queries, metadata objects, document posting or 1C configuration extensions
- You need machine-checkable proof of a standards check before a commit
- You need a clear map of which standards apply to a given situation instead of hoping the model recalls all three hundred of them
Not a fit when
- The project is not on 1C: the standards maps are specific to the platform
- There is no access to https://ai.v8std.ru/mcp and no local cache was built per the instructions
- You need a static analyzer or syntax checker: the harness only checks that an evidence trail exists, not the quality of the decision
Example request
Before committing, run the v8std standards check in gate mode against the changed configuration objectsLimitations
The validator runs offline and checks only the format of evidence lines, not their truthfulness: a made-up standard id will formally pass. The sentinel check catches an unreachable service or its pointer rolling back, but not the map itself falling behind the service. The map is a snapshot dated by last_reviewed_at, and keeping it current is the repository owner's responsibility. The repository does not contain the text of the 1C standards themselves, only ids and titles; the actual requirements are read via v8std.ru or ITS. Node.js 18 or newer is needed for the validator.
How to disable. Remove the skill from the agent's skills directory and delete the v8std server from your MCP client configuration.
FAQ
What if a standard is not on the situation map?
The skill requires at least one v8std_search call per work phase, so the map does not freeze at the moment it was created.
What is the difference between lint and gate mode?
lint only checks the formatting of found evidence lines and treats zero entries as a clean pass. gate requires at least one entry of any type and turns zero entries into a failure, which makes it suitable for blocking a commit.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA skill that checks BSL modules and Form.xml against the 1C development standards and 1C:Compatible requirements, with rules taken from APK
A set of skills, rules and MCP servers for 1C Enterprise 8.3 development where the agent works from real code and docs, not from memory
A skill for fast 1C extension development: an edit-load-test loop, storage discipline and AI features through TAB's AI Library
A plugin bundling 30 skills for 1C development standards based on v8std, plus a task pipeline from planning to release with approval and code-review gates
The 1c-dev Claude Code plugin: discussing a 1C task in dialogue, a technical spec, dependency-aware steps, and executing one verified step at a time
Skills covering the full 1C:Enterprise 8.3 development cycle, from XML sources to publishing and web client testing
README in short
The README describes the problem of a completed standards check being indistinguishable from a skipped one, and a four-layer solution: a situation map, mandatory search, a service sentinel check and machine validation of evidence lines. It includes a layer table, an example of four evidence-line types (applied, skipped, discovered, sentinel), a quick start covering the MCP connection and validator commands, the difference between lint and gate modes, and a separate honesty section: the harness does not analyze code, does not verify that standards exist, and does not guarantee the map is current. It credits the standards text to its 1C rights holder, noting the repository only holds ids. MIT license on the repository's own code.
README badge
Original SKILL.md
--- name: v8std-standards-harness description: > Use when writing, reviewing, or designing 1C:Enterprise (BSL) code and configuration metadata — enforces a fail-closed check against official 1C development standards (v8std) instead of relying on the agent to remember them. Triggers on: writing a query, creating or changing a metadata object (catalog, document, register, form, role), document posting and register movements, export procedures, client-server transitions, privileged mode, localization, configuration extensions, and any BSL code review. Produces machine-readable evidence lines that a validator can gate on, so a skipped standards check cannot pass silently. Not for non-1C codebases. --- # Обвязка для работы со стандартами 1С (v8std) Обвязка вокруг MCP-сервиса стандартов разработки 1С (https://ai.v8std.ru/mcp). Решает одну конкретную задачу: не дать агенту молча пропустить сверку со стандартами.