contract

Governes project contracts via a versioned, auditable registry with guarded mutations and lifecycle verbs.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill contract-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/contract
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill contract-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A project often depends on stable, clearly defined contracts (schemas, endpoints, and docs). This skill provides a centralized, versioned, date-stamped registry under contracts/ with a lock mechanism and an append-only ledger to ensure changes are auditable and controlled.

Core Features & Use Cases

  • Contract registry and versioning: stores each contract as a stamp with kind (schema, endpoint, doc), version history, and status (draft, etc.), plus an is_locked flag.
  • Guarded edits: a PreToolUse hook blocks hand-edits under contracts/ to force using /contract for all mutations, ensuring traceability.
  • Lifecycle verbs: init, status, new, update, bump, lock, unlock, off, check; supports auditing and governance during changes across a project.

Quick Start

Initialize the contracts folder and add a new contract with /contract init followed by /contract new my-contract --kind endpoint --why "initial draft".

Frequently Asked Questions about contract

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

FAQPage Schema
How do I prevent manual edits to API schemas and enforce controlled contract changes?

To prevent manual edits to API schemas, you can enforce controlled contract changes using a guard hook that blocks hand-edits in the contracts directory. This forces all schema mutations through a dedicated command, ensuring traceability and compliance.

How do I create an auditable ledger for project endpoint definitions?

You create an auditable ledger for endpoint definitions by initializing a contracts registry that logs all mutations. This append-only ledger records every change, supporting traceable and compliant contract management across your project.

Does the guard hook block direct file modifications in the contracts directory?

Yes, the guard hook blocks direct file modifications in the contracts directory. It enforces a strict mutation workflow by intercepting hand-edits, requiring all updates to go through the designated command.

How do I initialize a new contract registry and add an endpoint definition?

To initialize a new contract registry, run the init command to set up the folder structure, then use the new command with parameters for kind and reason. This creates a versioned, date-stamped stamp for your endpoint definition.

What are the limitations of using a locked contract registry for schema management?

A locked contract registry requires using specific lifecycle verbs for all mutations, preventing quick hand-edits. This strict workflow may add overhead for rapid prototyping but ensures compliant, traceable schema management.