contract-registry

Register external contracts and lifecycle states in a centralized registry.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ebijun1007/vibe-coding --skill contract-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-registry
Source: https://github.com/ebijun1007/vibe-coding/tree/main/.claude/skills/contract-registry
Command: npx skills add https://github.com/ebijun1007/vibe-coding --skill contract-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and track outward-facing commitments (APIs, CLI flags, ENV vars, and file formats) so teams have plan-time visibility, governance, and a single source of truth for contract lifecycle states.

Core Features & Use Cases

  • Centralized registry for public and internal contracts, including lifecycle statuses (stable, deprecated, removed)
  • Plan-time reference with ADR linkage to guide migrations and compatibility decisions
  • Lightweight documentation surface at .claude/contracts/registry.md for discoverability and compliance

Quick Start

Use the contract-registry skill to track and reference external API contracts and lifecycle states in planning sessions.

Frequently Asked Questions about contract-registry

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

FAQPage Schema
How do I track API contract lifecycle states and deprecations across product teams?

A contract registry centralizes outward-facing commitments like APIs, CLI flags, ENV variables, and file formats into a single source of truth, giving teams plan-time visibility and governance over compatibility decisions and migrations.

What's the best way to maintain a centralized API contract registry for compliance and governance?

A contract registry centralizes outward-facing commitments like APIs, CLI flags, ENV variables, and file formats into a single source of truth, giving teams plan-time visibility and governance over compatibility decisions and migrations.

Can I use a contract registry to track CLI flags and ENV variables alongside internal APIs?

A contract registry centralizes outward-facing commitments like APIs, CLI flags, ENV variables, and file formats into a single source of truth, giving teams plan-time visibility and governance over compatibility decisions and migrations.

How do I reference deprecated API contracts during plan-time migration decisions?

A contract registry centralizes outward-facing commitments like APIs, CLI flags, ENV variables, and file formats into a single source of truth, giving teams plan-time visibility and governance over compatibility decisions and migrations.

Do I need an existing ADR process to manage API contract lifecycle states effectively?

A contract registry centralizes outward-facing commitments like APIs, CLI flags, ENV variables, and file formats into a single source of truth, giving teams plan-time visibility and governance over compatibility decisions and migrations.