skills.rest
kreuzberg-dev
kreuzberg-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

polyrepo-boundaries

Determines repository ownership and coordinates cross-repository fixes across sibling Git repositories.

9.2k|581|Updated Jan 31, 2025
Search Tags:#Git#Rust#polyrepo#dependency-management#release-coordination#cross-repository#api-ownership
One-click install
npx skills add https://github.com/kreuzberg-dev/kreuzberg --skill polyrepo-boundaries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polyrepo-boundaries
Source: https://github.com/kreuzberg-dev/kreuzberg/tree/main/.ai-rulez/skills/polyrepo-boundaries
Command: npx skills add https://github.com/kreuzberg-dev/kreuzberg --skill polyrepo-boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a fix or API change spans multiple sibling repositories (Xberg, Alef, enterprise, crawler, LLM, OCR), it is easy to commit changes in the wrong repo, mix two repositories in one commit, or publish a consumer before its dependency. This Skill defines clear ownership boundaries and the correct coordination order.

Core Features & Use Cases

  • Ownership Mapping: Assigns each concern to its owning repository, such as reusable Rust primitives in xberg, generator defects in alef, LLM client behavior in liter-llm, and SSRF protection at the crawlberg transport boundary.
  • API Placement Guidance: Decides whether a primitive belongs in the Rust crate, in language bindings, or stays Rust-only without an FFI wrapper.
  • Release Coordination: For a cross-repo fix, identifies the lowest owning layer, orders dependency releases, and verifies each repository independently.
  • Use Case: A bug in generated Python bindings traces back to the Alef generator. Instead of patching around it in Xberg, this Skill directs you to fix the reusable cause in Alef, publish it, then update the consumer.

Quick Start

Ask the AI to determine which repository should own a fix that affects both Xberg and one of its sibling repositories, and to outline the commit and release order.

Frequently Asked Questions about polyrepo-boundaries

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

FAQPage Schema
How do I decide which repository owns a cross-repo fix?▼

Identify the lowest layer that owns the behavior: reusable Rust primitives belong in xberg, generator defects in alef, LLM client behavior in liter-llm, and crawler network policy in crawlberg. Fix the reusable cause at the owning layer rather than working around it in a consumer.

How do I coordinate a fix that spans multiple repositories?▼

Commit and publish the dependency repository first, then update the consumer to a version containing the fix. Verify each repository independently and never include changes from two repositories in one commit.

When should a Rust primitive be exposed in language bindings?▼

Expose a primitive in bindings only when it forms a coherent supported language API. Rust-only public functionality does not need an FFI wrapper, and compatibility policy applies to public APIs, not private internals.

Where should SSRF protection be implemented in a crawler stack?▼

Place SSRF protection at the component that performs the outbound request, which is crawlberg. Callers may add stricter policy on top, but they cannot replace the transport boundary.

When should I not use this polyrepo coordination guidance?▼

Do not use it for a self-contained edit within a single repository, such as a change confined to Xberg. It is intended only when work spans sibling repositories with independent releases.

Related Skills

Explore More Software Engineering Skills→
8Dionysus8Dionysus
2

aoa-workspace-recon

Map AoA workspace ownership and supporting surfaces before cross-repo work.

Community
Basic
steveclarkesteveclarke
1

release

Automate Superthread version bumps, changelog generation, and tag creation.

Community
Intermediate
davila7davila7
30.5k

test-fixing

Diagnose and fix failing tests by grouping errors and resolving root causes systematically.

Community
Intermediate
makeupmakeup
47

release-module

Automate Lerna-managed monorepo package releases with versioning and npm publishing.

Official
Advanced