Use this workflow when your Kodexa configuration lives in a Git repository or you want it to. For one-off operations, use the KDX CLI resource operations directly.
The Workflow
The normal loop is: Claude Code helps you work inside the repository. The KDX CLI is still the tool that talks to Kodexa.What Claude Code Should Help With
Use the skills for resource authoring, cleanup, and review:
For new workflow orchestration, start with Activity Plans. A Task is the human work item inside the process; the Activity Plan is the reusable process definition.
What Stays In Git
A typical metadata repository includes:sync-config.yaml, and .sync-state/. Do not commit API keys, secrets, generated logs, or local scratch files.
Human Review Still Matters
Claude Code should draft and modify configuration, but a developer or platform owner should still review:- Business meaning: Does the Activity Plan match the real process?
- References: Do task templates, forms, data definitions, modules, bridges, and knowledge sets exist in the target organization?
- Scope: Are changes limited to the intended project or reusable resource?
- Safety: Are secrets referenced by name instead of written into YAML?
- Deployment behavior: Does
kdx sync push --dry-runorkdx sync deploy --dry-runshow only the expected changes?
Pages In This Section
Install the Kodexa Skills
Install the Claude Code plugin and learn how skills are invoked.
Author Metadata
Use Claude Code to safely create and edit Kodexa configuration in a Git repository.
Sync with KDX
Pull, validate, dry-run, push, and deploy metadata with the KDX CLI.
KDX Sync Reference
Go deeper on sync configuration, manifests, conflict detection, and CI/CD.
