buf-cli-lint-breaking-buildlisted
Install: claude install-skill testland/qa-skills
# buf-cli-lint-breaking-build
## Overview
Wraps three buf CLI commands - `build`, `lint`, `breaking` - as the
proto-PR gate, per
[buf.build/docs/cli/quickstart/](https://buf.build/docs/cli/quickstart/).
The catalog of what counts as breaking and why lives in
[references/versioning-strategy.md](references/versioning-strategy.md)
(+ [references/buf-breaking-rules.md](references/buf-breaking-rules.md)).
## When to use
- Adding buf as the proto lint + breaking-change gate on a new
repo.
- A PR changes `.proto` files - need to gate the merge.
- Investigating a `buf breaking` failure - what rule fired?
- Configuring buf for a monorepo with multiple proto modules.
## Authoring
### Install
Per buf docs, install via Homebrew, Go install, or release binary.
Version 1.32.0 or higher is required. Verify:
```bash
buf --version
# 1.32.0 or higher
```
### Configure `buf.yaml`
The v2 format per
[buf.build/docs/cli/quickstart/](https://buf.build/docs/cli/quickstart/):
```yaml
version: v2
modules:
- path: proto
lint:
use:
- STANDARD
breaking:
use:
- FILE # default; choose per references/versioning-strategy.md
```
`STANDARD` is the recommended lint rule set; it enforces
conventions like "Field name should be lower_snake_case" and
"Service name should be suffixed with Service".
The choice of `breaking.use` (FILE / PACKAGE / WIRE_JSON / WIRE)
follows the per-deployment-model logic in
[references/versioning-strategy.md](references/versioning-strategy.md).
###