code-search

Search and analyze BSL code, metadata, and call graphs in 1C:Enterprise configurations.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill code-search-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-search
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/code-search
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill code-search-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Locating implementations, callers, event handlers, and execution flow inside large 1C:Enterprise configurations is slow with plain text search, because BSL code is spread across modules, forms, and metadata objects. This Skill routes code exploration through the Unica MCP index so you can find definitions, outlines, and call relationships without reading entire modules. ## Core Features & Use Cases - Indexed code search: Use unica.code.search with semantic, symbol, and lexical roles to find text, query fragments, captions, and identifiers across a source set. - Definition and outline lookup: Resolve exact procedure or function definitions with unica.code.definition and preview large modules with unica.code.outline before reading them. - Call graph analysis: Query unica.code.graph for callers, callees, neighbors, and impact analysis of a method or metadata node. - Metadata context: Inspect object structure, roles, event subscriptions, and functional options with unica.meta.info and map the workspace with unica.project.map. - Use Case: You need to understand how document posting works in a configuration. Resolve ОбработкаПроведения via unica.code.definition, then ask unica.code.graph for its callers to trace the full posting flow. ## Quick Start Ask the assistant to find where the ОбработкаПроведения procedure is defined and which modules call it in the current 1C workspace.

Frequently Asked Questions about code-search

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

FAQPage Schema
How do I find where a BSL procedure is defined in 1C?▼

Use unica.code.definition with the procedure or function name to get exact definition locations, especially for exported methods. For large candidate modules, call unica.code.outline first to see regions, header context, and method ranges before reading the file.

How do I find all callers of a method in a 1C configuration?▼

Use unica.code.graph with mode set to callers and the method node id, for example method:CommonModule.Продажи.ОбработкаПроведения. It also supports callees, neighbors, and impact analysis when the node id is known or resolvable.

What is the sourceSet parameter in unica code search?▼

sourceSet is the name of a source set defined in v8project.yaml, not a fixed constant. Resolve it with unica.project.map for the current workspace; the value main in examples is illustrative, not a default.

When should I use shell search instead of the Unica MCP tools?▼

Use shell search like rg only after the relevant unica.code and unica.meta calls did not close the context gap, or for repository files outside the public Unica index. Report what was tried when the fallback matters to the answer.

Why does unica.code.search return partial or empty results?▼

Inspect the termination field: null means ok or empty, while codes like dependencyPending with detailCode buildingIndex mean the index was still building when the deadline hit. Keep results from completed roles and retry later if semantic evidence is still needed.