kandev-config-import

Synchronize .kandev/ configuration files to the office database.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/AvatarGanymede/pcraft --skill kandev-config-import
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kandev-config-import
Source: https://github.com/AvatarGanymede/pcraft/tree/main/apps/backend/internal/office/configloader/skills/kandev-config-import
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill kandev-config-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the process of applying configuration changes made in the .kandev/ folder directly to the office database, ensuring consistency between source code and runtime settings.

Core Features & Use Cases

  • Apply Config Changes: Automates the synchronization of configuration changes between source code and the database.
  • Version Control: Supports the import of configurations from commits, enabling rollbacks and version control.
  • Use Case: For a developer to apply new settings from a code commit that modifies configurations stored in the .kandev/ folder.

Quick Start

Import the latest configuration changes with the command: kandev config import --workspace <workspace-id>

Frequently Asked Questions about kandev-config-import

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

FAQPage Schema
How do I synchronize configuration files from source code to a database?▼

Synchronizing configuration files to a database is done by importing changes from the .kandev/ directory. This ensures runtime settings reflect source code configuration by handling diffs and approvals for committed changes.

How do I apply configuration changes from a version control commit to runtime settings?▼

Applying configuration changes from a commit requires importing configurations from the .kandev/ folder. This process supports version control integration, enabling rollbacks and ensuring consistency between source code and the database.

What is the best way to automate office database synchronization with version control?▼

Automating office database synchronization is best handled by importing configuration changes committed in version control. This ensures runtime settings reflect source code configuration without manual database updates.

Can I rollback database configuration changes using version control integration?▼

Rolling back database configuration changes is supported through version control integration. Importing configurations from specific commits enables rollbacks and ensures runtime settings reflect the desired source code state.

How do I handle diffs and approvals for configuration management?▼

Handling diffs and approvals for configuration management is automated by importing changes from the .kandev/ directory. This process ensures runtime settings reflect source code configuration by processing committed configuration changes.

Why does my office database configuration not match my source code settings?▼

Office database configuration mismatches occur when runtime settings are not synchronized with source code. Importing configuration changes from the .kandev/ folder ensures consistency between source code and the database.