skills.rest
jfriisj
jfriisjCOMMUNITY
Explore all skills by this author →
GitHub

cross-repo-contract

Enforces cross-API contract definitions and versioning across repositories.

Updated Mar 20, 2026
Search Tags:#typescript#versioning#api#validation#governance#contract#cross-repo
One-click install
npx skills add https://github.com/jfriisj/coding-agents --skill cross-repo-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cross-repo-contract
Source: https://github.com/jfriisj/coding-agents/tree/main/.github/skills/cross-repo-contract
Command: npx skills add https://github.com/jfriisj/coding-agents --skill cross-repo-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains cross-repository API contracts through local definitions and type validation. Integrates strictly with Obsidian/Planka via Native MCP to coordinate breaking changes. Use this skill when implementing API endpoints or clients, proposing contract changes, or validating contract adherence across repositories.

Core Features & Use Cases

  • Contract discovery and tooling: Before implementing any API endpoint or client, check for contract definitions in api-contract/ or .contracts/. If neither exists and you are implementing API endpoints, propose creating an api-contract/ directory following the standard structure.
  • Coordination triad: Aligns changes across Source Code, Obsidian Graph, and Planka board to maintain consensus and track impact.
  • Handoff & governance: Document changes, bump versions, and update relevant notes to ensure traceability and governance.

Quick Start

Run a cross-repo contract workflow by locating contract definitions in api-contract/ or .contracts/, aligning changes in version.ts, and updating Obsidian and Planka notes.

Frequently Asked Questions about cross-repo-contract

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

FAQPage Schema
How do I enforce cross-repo API contracts across multiple repositories?▼

Cross-repo API contracts are enforced by reading local definitions from api-contract/ or .contracts/ directories and applying type validation. This ensures endpoints and clients align with the agreed structure across repositories.

What is the best way to coordinate breaking API changes across repositories?▼

Breaking API changes are coordinated by aligning updates across source code, Obsidian graphs, and Planka boards. This triad approach maintains consensus and tracks the impact of version bumps across repositories.

How do I validate API contract adherence when implementing new endpoints?▼

API contract adherence is validated by checking for definitions in api-contract/ or .contracts/ before implementation. If neither directory exists, you propose creating an api-contract/ directory following the standard structure.

Do I need TypeScript to manage cross-repo API contract versioning?▼

TypeScript is used for cross-repo API contract versioning by requiring version bumps in version.ts. This enables local type validation and ensures traceability when contracts change across repositories.

Why does API contract validation require updating Obsidian and Planka notes?▼

Updating Obsidian and Planka notes is required for governance and traceability when API contracts change. This coordination triad ensures breaking changes are documented and tracked across source code and project management boards.

When should I propose creating an api-contract directory for my repository?▼

An api-contract/ directory should be proposed when implementing API endpoints if no contract definitions exist. This establishes a standard structure for cross-repo coordination before endpoint or client implementation begins.

Related Skills

Explore More Software Engineering Skills→
adelabdelgawadadelabdelgawad

schema-type-consistency

Align Python Pydantic schemas with TypeScript types and CamelCase JSON contracts.

Community
Advanced
jfriisjjfriisj

analysis-methodology

Run structured root-cause analysis investigations with confidence classification and gap tracking.

Community
Advanced
jfriisjjfriisj

planka-workflow

Synchronize roadmap Epics to Planka with Markdown and MCP tools.

Community
Advanced
ultramaxoAIultramaxoAI

typed-service-contracts

Enforce end-to-end type safety for frontend-backend API contracts with Zod and TypeScript.

Official
Advanced