mcpbeat

Changelog

hashicorp/changelog

Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

377 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 changelog

The instruction itself

4 sections, as written by the author

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

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

Skill: Add Changelog Entry

Generate a .changelog/<PR_NUMBER>.txt entry for a GitHub Pull Request, commit it on the current branch, and push.

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

When to use

Trigger this skill when the user:

  • Says "add changelog", "create changelog entry", "write a release note", or similar.

Do not trigger for:

  • Edits to CHANGELOG.md directly (that file is generated — never modify it by hand).
  • PRs that are docs-only, test-only, code refactors, or dependency bumps with no operator-visible effect.

Do not generate a changelog file if the PR changes do not affect the terraform practitioners in the end.

Do not look at pre-existing changelog files when given the PR, not even if it is present in the diff.

Inputs

  • The <PR_NUMBER> and diff are available from the PR context for which the cloud agent was invoked.

Show, commit and push

  • Print the generated file contents back to the user.
  • Run:
   git add .changelog/<PR_NUMBER>.txt
   git commit -m "Add CHANGELOG for #<PR_NUMBER>"
   git push
  • Never run git push --force, --force-with-lease, or --no-verify. Never switch or create branches.

How to use it

Copy the folder

Take hashicorp/changelog 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.