Stats
Actions
Tags
From gobreaker
Detect breaking changes in a Go project's public API. Use when: checking API compatibility before release, reviewing PRs for breaking changes, comparing two git refs or tags, or auditing Go API modifications. Triggers on: "check breaking changes", "API compatibility", "is this a breaking change", "compare API", "gobreaker".
How this skill is triggered — by the user, by Claude, or both
Slash command
/gobreaker:checkThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect breaking changes in the current Go project using `gobreaker`.
Detect breaking changes in the current Go project using gobreaker.
Check that gobreaker is installed:
which gobreaker
If not found, stop and tell the user to install it first:
go install github.com/flaticols/gobreaker/cmd/gobreaker@latest
Do NOT install it automatically.
Run gobreaker from the repository root. Use $ARGUMENTS if the user provided refs,
otherwise default to comparing the default branch against the working directory:
cd $(git rev-parse --show-toplevel)
gobreaker $ARGUMENTS
If the user specified --path or -p, use filesystem mode:
gobreaker -p $ARGUMENTS
Based on the gobreaker output, provide a structured summary:
If gobreaker exits with code 1, breaking changes were found — emphasize this clearly. If no changes are detected, confirm the API is stable.
npx claudepluginhub flaticols/gobreaker --plugin gobreakerApplies modern Go syntax guidelines and features (slices, maps, cmp, min/max, etc.) based on project's detected Go version from go.mod. Avoids outdated patterns.
Detect breaking changes in Claude Code updates by comparing current API surface against changelog. Maps impacts to specific plugin files.
Detects breaking changes in REST, GraphQL, and gRPC API contracts. Compares OpenAPI schemas and protobuf defs to baselines, classifies severity, validates semver, runs Pact tests, generates reports.