codeledger

Track AI-generated code contributions in Git repositories using checkpoint workflows.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/jaguarliuu/CodeLedger --skill codeledger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codeledger
Source: https://github.com/jaguarliuu/CodeLedger/tree/main/skill/codeledger
Command: npx skills add https://github.com/jaguarliuu/CodeLedger --skill codeledger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeLedger tracks AI-generated vs human-authored code changes to support auditing and ensure attribution compliance across software projects.

Core Features & Use Cases

  • AI vs human attribution for commits integrated with Git notes for centralized auditing.
  • Mandatory pre-checkpoint and post-checkpoint workflow to capture changes before and after coding sessions.
  • Bundled binaries in the skill's bin directory enable seamless local execution of ledger commands without system-wide installation.

Quick Start

Install the CodeLedger skill under your .claude/skills/ and use the bundled binaries in the skill/bin directory. Before writing code, run ledger checkpoint pre; after finishing edits, run ledger checkpoint post; then commit as usual to record attribution.

Frequently Asked Questions about codeledger

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

FAQPage Schema
How do I track AI-generated code in Git commits for auditing?

Track AI-generated code in Git commits by running mandatory pre- and post-checkpoint workflows before and after coding sessions, capturing AI versus human edits and recording attribution data using Git notes for centralized auditing.

What is AI code attribution and why is it needed in software projects?

AI code attribution distinguishes AI-generated edits from human-authored changes in a repository, supporting compliance auditing and ensuring accurate tracking of AI contributions across Git-based software development projects.

How do I enforce a pre-checkpoint and post-checkpoint workflow for AI attribution?

Enforce pre-checkpoint and post-checkpoint workflows by running a ledger command before writing code to start tracking, then running the post command after finishing edits before a standard Git commit to record attribution accurately.

Do I need system-wide installation to audit AI code contributions locally?

No, system-wide installation is not required. The tool uses bundled binaries located in its bin directory, enabling seamless local execution of ledger commands directly within your software project environment.

Can I use Git notes for centralized auditing of AI versus human code changes?

Yes, you can use Git notes for centralized auditing of AI versus human code changes. The tool integrates attribution data directly into Git notes, allowing auditors to review AI contributions alongside standard commit history.

What are the limitations of using bundled binaries for AI code attribution?

Bundled binaries limit execution to the local skill directory and the specific supported Git-based project environment. Attribution accuracy strictly depends on following the mandatory pre-checkpoint and post-checkpoint workflow before commits.