ckl-edit

Modify code in indexed projects with provenance and auditable history.

Updated May 5, 2026

Search Tags:#provenance #refactor #session #code #edit #knowledge-graph #audit-trail

Ready to run

npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-edit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ckl-edit
Source: https://github.com/Alex980102/ckl-skill/tree/main/skills/ckl-edit
Command: npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Edit operations with provenance and an auditable history ensure accountability for code changes across projects.

Core Features & Use Cases

Provenance-aware edits: each change emits an Edit nutrient and links to the knowledge graph.
Batch and session support: group related edits and writes into a single auditable process.
Wide command coverage: supports edit, write, apply, mv, mkdir, rm, session for end-to-end workflows.

Quick Start

Edit a file in an indexed project and attach provenance to the change via the Edit nutrient.

Frequently Asked Questions about ckl-edit

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

FAQPage Schema

How do I make auditable code edits with provenance?▼

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.

Can I group multiple file refactors into a single auditable session?▼

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.

What is provenance in the context of a code knowledge graph?▼

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.

Do I need an indexed project to apply batch refactors and track an audit trail?▼

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.

What code edit operations are supported for tracking provenance?▼

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.

Why use an audit trail for code modifications instead of standard version control?▼

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.