ckl-edit

Auditable code edits with provenance are applied by emitting an Edit nutrient for each change and linking it to the knowledge graph. This ensures accountability by recording the origin and history of modifications within indexed projects.

Yes, you can group multiple file refactors into a single auditable session. The skill provides batch and session support, allowing you to group related edits, writes, and renames into one unified process for comprehensive provenance tracking.

Provenance in a code knowledge graph is the auditable history attached to code changes. It records the origin of modifications by emitting an Edit nutrient for each operation, ensuring that every edit is traceable and accountable within the indexed project.

Yes, you need an indexed project and the ckl binary (version 0.5.7 or higher) to apply batch refactors. The skill relies on the indexed project structure to integrate edits with the knowledge graph and enforce the audit trail.

Supported code edit operations for tracking provenance include edit, write, apply, mv, mkdir, rm, and session. These commands allow you to modify existing files, write new ones, rename files, and batch-refactor while maintaining an auditable history.

An audit trail for code modifications provides provenance-aware tracking by linking every change directly to the knowledge graph via Edit nutrients. Unlike standard version control, it enforces accountability at the edit level within indexed projects for detailed session history.