proto-split
OfficialSplit multi-service protos into clean domains
Software Engineering#code generation#configuration#protobuf#grpc#service boundaries#proto splitting#forge lint
Authorreliant-labs
Version1.0.0
Installs0
System Documentation
What problem does it solve?
You have a single .proto file that incorrectly contains multiple service definitions, which makes forge lint fail and causes ambiguous generation outputs and tight cross-service coupling.
Core Features & Use Cases
- Identify what to split by inventorying services, RPCs, and message ownership, then classifying messages as service-owned, shared, or removable.
- Restructure the proto layout into one service per .proto plus an optional shared types file for cross-service value messages.
- Update build and configuration by fixing imports, adjusting forge.yaml services entries, moving handler code, and regenerating code so lint/build/test stay green.
Quick Start
Run the split plan for your aggregated proto by creating proto/shared/v1/types.proto for truly shared messages and then moving each service into its own proto/services/<service>/v1 file before updating forge.yaml and regenerating with forge generate.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: proto-split Download link: https://github.com/reliant-labs/forge/archive/main.zip#proto-split Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.