Skill Detail
Lint protobuf definitions for style and correctness before code generation and review churn begin with protolint
Catch naming, formatting, and protobuf rule violations early so generated clients and reviews are cleaner.
Code Quality & ReviewMulti-Framework
Code Quality & Review
Multi-Framework
Security Reviewed
⭐ 685 GitHub stars
⬇ 2.2k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill lint-protobuf-definitions-for-style-and-correctness-before-code-generation-and-review-churn-begin-with-protolint
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
protolint installation, protobuf source files, and optional CI or pre-commit integration where lint findings should gate changes
Install & setup
Install protolint from the upstream binary, package, or Go-based installation instructions, then run it against the target .proto files or repository and review or gate on the reported violations.
Author
yoheimuta
Publisher
Individual
Last updated
Apr 17, 2026
Quick brief
Use protolint when an agent needs to validate .proto files for style consistency and correctness before generating code or opening review. A user should invoke this instead of working with protobuf tooling normally when the job is static linting of schema files, not compilation, service runtime work, or broader API platform management. The scope boundary is narrow and skill-shaped: linting protobuf source definitions and returning actionable findings, not listing a generic protobuf library or SDK.