db-list

Manage 1C database registries in .v8-project.json files.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill db-list-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-list
Source: https://github.com/msrv-tech/skills/tree/main/db-list
Command: npx skills add https://github.com/msrv-tech/skills --skill db-list-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage the registry of 1C databases stored in the project-level .v8-project.json, removing manual editing and human error.

Core Features & Use Cases

  • List all configured databases with IDs, names, types, and connection hints.
  • Add, remove, or show details for specific databases interactively or via scripts.
  • Use cases include onboarding new projects, auditing database configurations, and preparing environments for automated deployments.

Quick Start

Run /db-list to display the current databases and follow interactive prompts to add or remove entries.

Frequently Asked Questions about db-list

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

FAQPage Schema
How do I manage 1C database configurations in a v8-project.json file?

You can manage 1C database configurations in a .v8-project.json file by listing, adding, removing, and showing database details interactively or via scripts. It reads and updates the databases array, persisting changes directly to disk to eliminate manual editing errors.

What is the best way to list all configured 1C databases in my project?

The best way to list configured 1C databases is using an interactive registry manager that reads the .v8-project.json file. It displays all entries with their IDs, names, types, and connection hints, providing a clear overview for onboarding and auditing without manual file parsing.

Can I add and remove 1C databases from the registry using automated scripts?

Yes, you can add and remove 1C databases from the .v8-project.json registry using automated scripts. The tool supports scripted contexts for preparing environments and automated deployments, providing optional interactive prompts for any missing required fields.

How does updating the v8-project.json database registry prevent configuration errors?

Updating the v8-project.json database registry programmatically prevents configuration errors by automating the modification of the databases array. This removes the risk of human error associated with manual JSON editing and ensures that connection hints and database types are consistently formatted.

Do I need any specific dependencies to manage a .v8-project.json file?

You do not need any specific dependencies to manage a .v8-project.json file with this tool, as it operates without external requirements. It directly reads and updates the project-level JSON configuration to help teams audit database setups and prepare environments.

When should I interactively add a database to the 1C project config instead of editing the JSON directly?

You should interactively add a database to the 1C project config instead of editing the JSON directly when onboarding new projects or auditing configurations. Interactive prompts ensure missing fields are correctly populated, preventing syntax errors and maintaining a valid databases array.