kandev-config-sync

Synchronize Office workspace configuration with the .kandev folder for export, import, and diff review.

733|110|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill kandev-config-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kandev-config-sync
Source: https://github.com/kdlbs/kandev/tree/main/apps/backend/internal/office/configloader/skills/kandev-config-sync
Command: npx skills add https://github.com/kdlbs/kandev --skill kandev-config-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Workspace configuration in Kandev lives in the Office database, but teams need a reviewable, committable representation on disk in the .kandev/ folder. This Skill keeps the two in sync so configuration changes can be exported, imported, seeded, and reviewed as diffs.

Core Features & Use Cases

  • Config Export: Write current workspace state (settings, agent profiles, projects, routines, triggers, user-imported skills) to disk for committing or handoff.
  • Config Import: Scan .kandev/workspaces/<slug>/, diff YAML against the database, and present a pending import diff for approval before changes land.
  • Use Case: A teammate commits .kandev/ changes to the repository. You use this Skill to review the pending import diff, approve safe changes, and reject unexpected destructive modifications before they reach the Office database.

Quick Start

Ask the agent to compare the Office database with the .kandev folder and show the pending config import diff for review.

Frequently Asked Questions about kandev-config-sync

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

FAQPage Schema
How do I export Kandev workspace configuration to disk?

Export workspace configuration through the UI at Settings > Config, which writes settings, agent profiles, projects, routines, triggers, and user-imported skills to the .kandev folder. There is no agentctl kandev config export command yet.

How do I import .kandev config changes into the Office database?

The Office service scans .kandev/workspaces/<slug>/, diffs the YAML files against the database, and presents a pending import diff for approval. Use the UI at Settings > Config; no CLI import command exists yet.

When should I use config export versus config import?

Export when committing configuration changes, diffing current state against the agreed setup, or handing a workspace to another machine. Import when a teammate committed .kandev changes, when seeding a fresh workspace, or when rolling back to an older commit.

What should I do if a config import diff shows destructive changes?

Reject the diff and investigate before approving. The import flow presents a pending diff for approval precisely so unexpected destructive changes never reach the Office database without human review.

Are system skills included in exported workspace configuration?

No. System skills are bundled with the kandev binary and are not part of user-exported configuration. Only user-imported skills appear in the exported config alongside settings, profiles, projects, routines, and triggers.