Agent skill
libcodegen
libcodegen - Protocol Buffer code generation. TypeGenerator, ServiceGenerator, and DefinitionGenerator transform .proto files into JavaScript types, gRPC service stubs, and type definitions. Use for generating code from protobuf schemas, automating service stub creation, and maintaining type consistency across services.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/libcodegen
SKILL.md
libcodegen Skill
When to Use
- Generating JavaScript types from Protocol Buffer schemas
- Creating gRPC service stubs automatically
- Updating generated code after .proto changes
- Maintaining type consistency across microservices
Key Concepts
TypeGenerator: Generates JavaScript classes from protobuf message definitions with proper type annotations.
ServiceGenerator: Creates gRPC service stubs with method signatures matching the proto service definitions.
DefinitionGenerator: Generates type definitions for IDE support and documentation.
Usage Patterns
Pattern 1: Generate types from protos
import { TypeGenerator } from "@copilot-ld/libcodegen";
const generator = new TypeGenerator("./proto");
await generator.generate("./generated/types");
Pattern 2: Generate service stubs
import { ServiceGenerator } from "@copilot-ld/libcodegen";
const generator = new ServiceGenerator("./proto");
await generator.generate("./generated/services");
Integration
Run via make codegen after modifying .proto files. Output used by libtype and
librpc.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?