kandev-config-export

Export office workspace configurations to a .kandev/ folder for version control.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the export of office workspace configurations to a version-controlled .kandev/ folder, eliminating the manual process of committing changes and making it easier to track and manage configuration changes over time.

Core Features & Use Cases

  • Automated Configuration Export: Exports workspace configurations to a .kandev/ folder for version control.
  • Version Control Integration: Facilitates commit of configuration changes to a git repository.
  • Diffing & Backup: Enables diffing of configuration states and provides a manual backup option.
  • Use Case: Ideal for teams that need to ensure configurations are in sync across environments and for auditing purposes.

Quick Start

Run the kandev-config-export skill to export the current office workspace configuration to the .kandev/ folder.

Frequently Asked Questions about kandev-config-export

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

FAQPage Schema
How do I automate office workspace configuration exports for version control?

Automating workspace configuration exports is achieved by writing settings to a .kandev/ folder, which allows you to track and manage configuration changes over time without manual file commits.

Can I commit workspace configuration changes directly to a git repository?

Yes, you can commit workspace configuration changes to a git repository. The export process facilitates version control integration by saving your current settings into the designated .kandev/ directory.

What is the best way to diff configuration states across different office environments?

Diffing configuration states is handled by exporting your workspace settings to the .kandev/ folder, enabling you to compare file changes and ensure configurations are in sync across environments.

Do I need specific permissions to export workspace configuration files to the .kandev directory?

Yes, you need appropriate permissions to access your workspace configuration files and write to the .kandev/ directory to successfully automate the export and backup process.

Why use a .kandev folder for workspace configuration management instead of manual backups?

Using a .kandev folder eliminates the manual process of backing up files, providing a structured approach to auditing configuration changes and ensuring team environments remain in sync.