db-list

Manages .v8-project.json registry to resolve 1C target databases by criteria including Git branch.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill db-list-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-list
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/db-list
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill db-list-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps you quickly keep the .v8-project.json registry of 1C information bases accurate, so Claude Code can correctly resolve the target database for builds, dumps, and connection-based tasks.

Core Features & Use Cases

  • Database registry control: list all configured bases, add new bases (interactive), remove bases by id, and show full details for a specific base or alias.
  • Smart target resolution: resolves the intended database by connection parameters, id/alias/name matching with morphology-aware alias handling, or by matching the current Git branch to branches (with fallback to default).
  • Operational workflow readiness: supports the connection-string format needed by other skills that rely on consistent database selection.

Quick Start

Ask the AI to show the configured 1C bases from your project by using the command: /db-list show dev.

Frequently Asked Questions about db-list

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

FAQPage Schema
How do I list configured 1C databases from the .v8-project.json registry?

You can list configured 1C databases by prompting the AI with a command like /db-list show dev. This reads the .v8-project.json registry and displays all available bases, aliases, and their connection parameters.

What is the best way to resolve a 1C target database for my current Git branch?

Database resolution matches your current Git branch against the branches field defined in the .v8-project.json registry. If the branch is not explicitly mapped, it automatically falls back to the default database entry.

How do I add or remove 1C information bases in my project configuration?

You can interactively add new bases or remove existing entries by id from the .v8-project.json file. This ensures the registry stays accurate for resolving connection parameters during builds and dumps.

Can I select a 1C database by alias or name instead of using an id?

Yes, target resolution supports selecting a database by id, alias, or name. It uses morphology-aware alias handling to match your input to the correct connection parameters in the registry.

How does database resolution precedence work when multiple parameters are provided?

Resolution precedence applies connection parameters first, then matches by id, alias, or name, and finally checks the current Git branch mapping. This ensures accurate connection-string generation for downstream tasks.