polyrepo-boundaries
GitHub定义多仓库工作区中各组件的API所有权与边界，规范跨库修复、依赖发布顺序及API放置策略。
Trigger Scenarios
Install
npx skills add xberg-io/xberg --skill polyrepo-boundaries -g -y
SKILL.md
Frontmatter
{
"name": "polyrepo-boundaries",
"type": "Playbook",
"title": "Polyrepo Boundaries",
"x-ai-rulez": {
"id": "polyrepo-boundaries",
"kind": "skill",
"metadata": {
"name": "polyrepo-boundaries"
}
},
"description": "Coordinate cross-repo fixes, API ownership and compatible sibling changes."
}
Polyrepo boundaries
Each sibling under the workspace root is an independent Git repository with its own history, release, CI, and governance. Pushing Xberg does not publish a sibling dependency.
Ownership
xberg: reusable Rust document-intelligence primitives, public Rust API, CLI/server surfaces, bindings, and Xberg CI/release packaging.xberg-enterprise: product and deployment behavior that consumes Xberg. Check it before removing or reshaping Rust primitives, even when the symbol is not exposed in language bindings.alef: binding, documentation, snippet, and e2e generation defects. Work around a generator defect in Xberg only when necessary; report and fix the reusable cause in Alef.liter-llm: reusable LLM client behavior, provider request construction, endpoint validation, and network-security controls owned by that client.crawlberg: crawling, URL retrieval, and crawler-specific network policy. Put SSRF protection at the component that performs the outbound request; callers may add stricter policy but cannot replace the transport boundary.sceptre: reusable Sceptre OCR models/runtime. Xberg owns its adapter, configuration, and integration behavior.
API placement
Keep reusable primitives in the Rust crate when enterprise or Rust callers need them. Bindings should expose a primitive only when it forms a coherent supported language API; Rust-only public functionality does not need an FFI wrapper. Compatibility and deprecation policy applies to public APIs, not private internals.
For a cross-repo fix, identify the lowest owning layer, coordinate the dependency/release order, and verify each repository independently. Commit and publish the dependency before updating a consumer to a version that contains the fix.
Version History
-
844bb91
Current 2026-11-03 09:37
移除旧版中禁止单提交包含两仓变更的绝对限制，新增跨库修复需识别最低所有权层、协调依赖发布顺序并独立验证的具体执行指南。
- 3be78fd 2026-10-19 16:31
- d8e4815 2026-08-28 18:31
