Menu
Apply config changes from the .kandev/ folder back into the office DB
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.
| name | kandev-config-import |
| description | Apply config changes from the .kandev/ folder back into the office DB |
| kandev | {"system":true,"version":"0.42.0","default_for_roles":["ceo"]} |
The mirror of kandev-config-export. Use when:
.kandev/ folderThe office service scans .kandev/workspaces/<slug>/ and diffs the on-disk YAML against the DB. Any divergence becomes a pending_import entry the CEO (or a user) must approve before it lands.
$KANDEV_CLI kandev config import --workspace $KANDEV_WORKSPACE_ID
(Implementation pending: see office-config spec. Until shipped, prefer the Settings → Config page.)
is_system flags — those are kandev-owned)is_system: true) — those flow from the binary on every kandev start. Editing them in .kandev/ is a no-op..kandev/.The import flow always shows a diff first. If you see a destructive change you didn't expect (e.g. "delete agent A-1"), reject the diff and investigate before applying.