Split multi-service protobuf files into one .proto per service with shared types.
npx skills add https://github.com/reliant-labs/forge --skill proto-split
Please help me install this Agent Skill. Skill: proto-split Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/proto-split Command: npx skills add https://github.com/reliant-labs/forge --skill proto-split
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.
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.
High-intent search queries and answers about installing and using this skill.
To split a multi-service protobuf file, you inventory services and messages, classify them, then create one .proto per service and extract shared value types into a shared file to reduce cross-service coupling.
Forge lint fails because it enforces single service declarations per file. When a proto contains multiple service definitions, it causes ambiguous generation outputs and tight cross-service coupling, requiring you to split the proto layout.
When splitting protos by service boundary, you classify messages as service-owned, shared, or removable. Truly shared cross-service value messages are extracted into a shared types file, such as proto/shared/v1/types.proto, to prevent duplication.
Yes, you must update forge.yaml with snake-form path service entries after splitting proto files. You also need to fix imports, move handler code, and regenerate code using forge generate instead of editing generated pb.go artifacts.
The best way to reduce cross-service coupling is to restructure legacy proto layouts into one service per file, extract shared types, forbid service-to-service proto imports, and enforce single service declarations per file during code generation.
reliant-labsGenerate Go and Next.js infrastructure from forge.v1-annotated proto contracts.
alo-expMigrate Silver Bullet projects from Claude Desktop SB to Forge-compatible setups.
reliant-labsDocument Forge proto file conventions and annotation rules for code generation.
FaysilAlshareefDesign gRPC service contracts and C# implementations for .NET microservices.
