mcpbeat

Breaking Changes

hashicorp/breaking-changes

Review a PR for possible breaking changes.

290 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
11023
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/hashicorp/terraform-provider-aws --skill breaking-changes

The instruction itself

3 sections, as written by the author

<!-- Copyright IBM Corp. 2014, 2026 -->

<!-- SPDX-License-Identifier: MPL-2.0 -->

Skill: Review PR For Breaking Changes

Assume the @maintainer persona.

Determine whether a GitHub Pull Request makes a breaking change. If so provide feedback on reasons for the breaking change and possible next steps.

If the PR does not make any breaking changes, note that.

Do NOT consider any breaking-change label applied to the PR.

Review only the code changes included in the PR.

Authoritative reference: docs/breaking-changes.md. When this skill and that document disagree, the document wins.

When to use

Trigger this skill when the user:

  • Provides a https://github.com/hashicorp/terraform-provider-aws/pull/<N> URL and asks for a breaking change review.
  • Says "review breaking change", or similar, with a PR URL.

Inputs

Required:

  • A GitHub PR URL. Extract <PR_NUMBER> with the regex /pull/(\d+).

If the user provides only a PR number, ask for the full URL (or confirm the repo is hashicorp/terraform-provider-aws).

How to use it

Copy the folder

Take hashicorp/breaking-changes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.