review

Orchestrates full code review of 1C BSL modules by delegating to specialized reviewer and writer agents.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill review-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/review
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill review-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing 1C:Enterprise BSL code manually is slow and inconsistent, especially across large extensions and change requests. This Skill automates the full review cycle: it resolves the review scope, collects evidence (linter diagnostics, naming and comment hygiene signals, project whitelists), delegates the verdicts to a dedicated code-reviewer agent, saves a structured report, and optionally routes findings to a writer agent for fixes with re-review. ## Core Features & Use Cases - Smart scope resolution: review a module, directory, extension, change request (ZN), or uncommitted git diff, with diff-focused boundaries that limit findings to changed procedures. - Evidence-driven review: aggregates linter signals, identifier hygiene (Latin characters in identifiers), comment hygiene, whitelist and mandatory-control checks before delegating to the reviewer agent. - Fix loop with re-review: after user confirmation, passes MUST_FIX findings to a code-writer agent and re-reviews (max 2 iterations); supports light review for trivial diffs and a prerelease mode for full-extension audits. - Use Case: You finished a change request touching several .bsl modules in an extension. Run the review to get a deduplicated findings report saved under the change's reports folder, then let the writer agent fix the critical findings and verify them automatically. ## Quick Start Ask the assistant to review the current BSL module or the uncommitted .bsl changes in the working tree and save the findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review 1C BSL code changes before committing?

Invoke the review without arguments: it defaults to a diff-focused review of uncommitted .bsl files in the working tree. Findings are limited to changed procedures, and a report is saved under the change's reports folder or temp/reports.

What is the difference between /review and /release-review?

/review is an operational review with release_mode=false, while /release-review runs prerelease mode with full-extension scope, release-hygiene antipattern checks, and an architectural explorer pass over all extension BSL files.

Can the review automatically fix the findings it reports?

Yes. After the report, the skill asks whether to fix MUST_FIX findings via the onec-code-writer agent, followed by a mandatory re-review with a maximum of two iterations. REFACTOR findings can be routed to a code-simplifier agent.

Does the review work when the linter or BSL LSP is unavailable?

Yes, it degrades gracefully: the reviewer prompt receives a Linter Signals block noting the tool is unavailable, and the final report summary includes a warning instead of failing.

When does the skill skip a full review for trivial changes?

When the diff contains only whitespace, comment-only, or rename-only changes, a light review runs linter, whitelist, identifier hygiene, and comment hygiene checks without invoking the reviewer agent. Use the --full flag to override.