skills.rest
MetaMask
MetaMaskOFFICIAL
Explore all skills by this author →
Website𝕏@metamaskGitHub

pr-changelog

Generate a CHANGELOG entry line from pull request code changes.

3.0k|1.6k|Updated Jul 18, 2018
Search Tags:#automation#changelog#validation#pull-request#release-notes#code-changes#user-facing
One-click install
npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-changelog
Source: https://github.com/MetaMask/metamask-mobile/tree/main/.agents/skills/pr-changelog
Command: npx skills add https://github.com/MetaMask/metamask-mobile --skill pr-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a concise and standardized CHANGELOG entry line for a pull request by analyzing code changes and determining whether they affect end users.

Core Features & Use Cases

  • Detects user-facing changes vs internal changes and outputs either a formatted CHANGELOG entry or null.
  • Enforces the required "CHANGELOG entry:" format for CI validation and supports bypass via the no-changelog label.
  • Helps maintain release notes consistency across PRs and speeds up changelog generation for collaborators.

Quick Start

Review a PR's diffs and provide a primary, past-tense summary of the user-facing impact, or return null if there is no user-facing change.

Frequently Asked Questions about pr-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog entry from pull request code changes?▼

To generate a changelog entry from pull request code changes, review the PR diffs and provide a primary, past-tense summary of the user-facing impact to produce a formatted CHANGELOG entry line.

How do I bypass changelog validation for internal pull requests?▼

To bypass changelog validation for internal pull requests, apply the no-changelog label to the PR, which marks non-user-facing changes as null and satisfies CI formatting requirements.

What is the required format for a pull request changelog entry?▼

The required format for a pull request changelog entry is a concise, past-tense summary line prefixed with CHANGELOG entry: to ensure release notes consistency and pass CI validation.

When should a pull request return null for the changelog entry?▼

A pull request should return null for the changelog entry when the code changes are strictly internal and do not introduce any user-facing changes that affect end users.

Can I automate release notes generation for user-facing changes?▼

You can automate release notes generation for user-facing changes by analyzing PR diffs to detect user impact and outputting a standardized CHANGELOG entry line for release documentation.

Does the changelog generator distinguish between user-facing and internal changes?▼

The changelog generator distinguishes between user-facing and internal changes by analyzing code diffs to determine end-user impact, formatting user-facing updates and returning null for internal ones.

Related Skills

Explore More Software Engineering Skills→
abretonc7sabretonc7s

pr-changelog

Analyze pull request diffs to generate user-facing changelog entries.

Community
Basic
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
dennisonbertramdennisonbertram
1

git-pr-create

Automate GitHub pull request creation with templates, labels, reviewers, and linked issues.

Community
Intermediate
oalansilvaoalansilva

release-notes-drafter

Draft release notes from merged PRs and commits.

Community
Intermediate