New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Changeset PR

by module-federation in module-federation/core

Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets…

MITAuto-check passed

Install Changeset PR

skills CLI
$ npx skills add module-federation/core --skill changeset-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install module-federation/core changeset-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/module-federation/core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/changeset-pr .claude/skills/changeset-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
changeset-pr
GitHub stars
2.7k
Token cost
~1.3k tokens
SKILL.md length
553 words
Files
5 (incl. scripts, references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets…

  • Works in 5 steps: Confirm whether a changeset is needed. → Identify the publishable package scope… → Create or edit one .changeset/*.md file. → …
  • A publishable package changed
  • SKILL.md covers Overview, Workflow, Decide Whether A Changeset Is… and Determine Scope, plus 4 more sections
  • Runs Python scripts from its folder; calls python3, git and pnpm

What it does

Changeset PR is an agent skill from module-federation/core. Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config. Use when a publishable package changed, when a PR is missing a changeset, when an existing changeset needs correction, or when Codex needs to confirm whether a branch should have a changeset at all.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/repo-conventions.md` and `scripts/inspect_changeset_scope.py`).

The repository describes itself as: Module Federation is a concept that allows developers to share code and resources across multiple JavaScript applications. The licence is MIT.

When your agent uses it

  • A publishable package changed
  • A PR is missing a changeset
  • An existing changeset needs correction
  • Codex needs to confirm whether a branch should have a changeset at all

Example prompts

  • “/changeset-pr”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm whether a changeset is needed.
  2. Identify the publishable package scope from the live branch diff.
  3. Create or edit one .changeset/*.md file.
  4. Validate the file against repo config and branch scope.
  5. Report the exact commands run and any ambiguity that remains.

What it can do on your machine

Read from SKILL.md and the folder at commit d139eed. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • git
    • pnpm
    • changeset

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changeset PR loads about 1.3k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 553 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from module-federation/core at commit d139eed, republished under its MIT licence (© module-federation). 553 words, ~1,253 tokens.

Download SKILL.mdSave it as .claude/skills/changeset-pr/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
changeset-pr
description
Create or update a `.changeset/*.md` file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config. Use when a publishable package changed, when a PR is missing a changeset, when an existing changeset needs correction, or when Codex needs to confirm whether a branch should have a changeset at all.

Changeset PR

Overview

Create a repo-correct changeset for the current branch, or update an existing one without widening scope unnecessarily. Verify both syntax and package scope before handoff.

Ground the changeset in the live branch diff, not stale branch intent. Always inspect the current branch state against its base before choosing package scope or release type.

Workflow

  1. Confirm whether a changeset is needed.
  2. Identify the publishable package scope from the live branch diff.
  3. Create or edit one .changeset/*.md file.
  4. Validate the file against repo config and branch scope.
  5. Report the exact commands run and any ambiguity that remains.

Decide Whether A Changeset Is Needed

  • Add a changeset when a publishable package behavior changes.
  • Do not add one for docs-only or non-behavioral repo changes unless the user explicitly wants release metadata anyway.
  • If unsure whether the change is user-visible enough to merit a release note, inspect existing changesets in .changeset/ and bias toward a short patch changeset rather than skipping silently.

Read references/repo-conventions.md when you need the repo-specific fixed-group, ignore-list, or release-flow details.

Determine Scope

First inspect the live branch state:

bash
git diff --name-status origin/main...HEAD
git diff --stat origin/main...HEAD
git log --oneline --decorate --no-merges origin/main..HEAD

Use that to separate real publishable-package behavior changes from repo-local docs, skills, tooling, or cleanup.

Start with the helper script:

bash
python3 .codex/skills/changeset-pr/scripts/inspect_changeset_scope.py --base origin/main

Use its output to separate:

  • touched publishable packages
  • ignored packages
  • fixed groups that will affect release planning

If the branch touches multiple publishable packages, include only the packages whose behavior actually changed. Do not add app/example packages from the ignore list.

Create Or Update The Changeset

Prefer editing an existing branch changeset when one already covers the same change. Otherwise create a new file in .changeset/ with the standard format:

md
---
"@module-federation/pkg-name": patch
---

Brief user-facing summary of the change.

Rules:

  • Keep the summary brief and release-note oriented.
  • Avoid implementation-detail dumps and nested bullets.
  • Use patch, minor, or major unless there is a specific reason to use none.
  • Quote package names in frontmatter.
  • Keep package scope tight even if the fixed group later broadens the computed plan.

The repo has a custom helper:

bash
pnpm run changegen

Use it only if the user explicitly wants generated changeset text or the touched package is already covered by its configured package paths. Otherwise write the file directly.

Show full SKILL.md (197 more words)Show less

Validate

There is no dedicated changeset validate command in the official CLI. Use these checks instead:

  1. Validate branch scope against the file:
bash
python3 .codex/skills/changeset-pr/scripts/inspect_changeset_scope.py --base origin/main --file .changeset/<file>.md
  1. Validate that Changesets can parse and plan the release:
bash
python3 .codex/skills/changeset-pr/scripts/run_changeset_status.py --verbose
  1. When machine-readable output is useful:
bash
python3 .codex/skills/changeset-pr/scripts/run_changeset_status.py --output /tmp/changeset-status.json

Interpretation:

  • status verifies parseability and computed release planning.
  • status does not prove the changeset is branch-local or minimal in this repo because other pending changesets may already exist.
  • Fixed-group packages can cause broader or higher bumps than the frontmatter alone suggests.
  • Prefer the helper script over direct pnpm exec changeset status in Codex runs because shell wrappers in non-TTY sessions can add /dev/tty noise or otherwise make the raw CLI output unreliable.

Update Existing Changesets

When asked to update a changeset for a branch or PR:

  • search .changeset/*.md for the affected package name first
  • prefer editing the existing file if it clearly belongs to the same branch work
  • avoid creating duplicate files for the same single change unless the branch intentionally has multiple release notes

After editing, rerun both validation steps.

Report Back

Always report:

  • whether the branch needed a changeset
  • which packages were included
  • which commands were run
  • whether changeset status succeeded
  • any fixed-group or ignored-package caveats

© module-federation, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in .codex/skills/changeset-pr of module-federation/core.

  • SKILL.md
  • agents/openai.yaml
  • references/repo-conventions.md
  • scripts/inspect_changeset_scope.py
  • scripts/run_changeset_status.py

Open the folder on GitHubat commit d139eed

Compare with similar skills

Changeset PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changeset PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changeset PR this skillmodule-federation/core2.7k—~1.3kAutomated safety check: PassMIT
Changesetwithastro/astro63k—~1.1kAutomated safety check: PassCustom licence
Changesetbiomejs/biome26k—~839Automated safety check: PassApache-2.0
Changesetudecode/plate17k—~1.3kAutomated safety check: PassCustom licence
Changesetwhitphx/stlite1.7k—~1.9kAutomated safety check: PassApache-2.0
Branchesredis/RedisInsight8.9k—~409Automated safety check: PassCustom licence

Similar skills

  • Changeset

    withastro/astro

    Official

    Create a changeset for the Astro monorepo. An agent skill from withastro/astro.

    63k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Changeset

    biomejs/biome

    Official

    A skill your agent uses when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit .changeset/.md release-note text.

    26k GitHub stars~839 tokensUpdated today
    DevelopmentAuto-check passed

  • Changeset

    udecode/plate

    Command: changeset

    17k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Changeset

    whitphx/stlite

    Create or update a changeset fragment (.changeset/.md) reflecting the changes made in the current session or branch.

    1.7k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Branches

    redis/RedisInsight

    Official

    Create and name git branches following project conventions. An agent skill from redis/RedisInsight.

    8.9k GitHub stars~409 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Conventional Branch

    github/awesome-copilot

    Official

    Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/).

    40k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from module-federation/core

  • Gh PR Metadata

    module-federation/core

    Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.

    2.7k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Local CI

    module-federation/core

    Run this repository's local CI parity commands and pnpm run ci:local jobs.

    2.7k GitHub stars~914 tokensUpdated today
    Auto-check passed

  • Sokra Mode

    module-federation/core

    Design, build, and maintain module-federation/core the way sokra (Tobias Koppers) built webpack 5: plugin architecture, container/sharing, runtime, caching, and reviews.

    2.7k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Sokra Mode

    module-federation/core

    Apply sokra's webpack design discipline to module-federation/core plugin architecture, runtime, caching, and reviews when asked for sokra mode or to review or build something like sokra would.

    2.7k GitHub stars~233 tokensUpdated today
    Auto-check passed

Questions about Changeset PR

What does Changeset PR do?

Create or update a .changeset/.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets…. Changeset PR is an agent skill from module-federation/core.md file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config.

When should I use Changeset PR?

Changeset PR fits situations like: A publishable package changed; A PR is missing a changeset; an existing changeset needs correction; Codex needs to confirm whether a branch should have a changeset at all.

How do I install Changeset PR in Claude Code?

Run `npx skills add module-federation/core --skill changeset-pr -a claude-code`. Or copy the skill folder (.codex/skills/changeset-pr in module-federation/core) into .claude/skills/changeset-pr in your project. Claude Code loads it when a task matches its description.

How do I install Changeset PR in Codex?

Run `npx skills add module-federation/core --skill changeset-pr -a codex`. Or copy the skill folder (.codex/skills/changeset-pr in module-federation/core) into .agents/skills/changeset-pr in your project. Codex loads it when a task matches its description.

Can I use Changeset PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add module-federation/core --skill changeset-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changeset-pr, .gemini/skills/changeset-pr, .github/skills/changeset-pr and .opencode/skills/changeset-pr in your project.

What does Changeset PR need to run?

Going by SKILL.md and its folder, Changeset PR needs Python for the scripts in its folder and the command-line tools its instructions call (python3, git, pnpm and changeset). Our summary lists: Python 3.

Does Changeset PR access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Changeset PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Changeset PR use?

Changeset PR is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changeset PR use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 386 tokens, read only when the agent opens those files.

What are the alternatives to Changeset PR?

Skills that share tags, products or a category with Changeset PR: Changeset (withastro/astro, 63k stars), Changeset (biomejs/biome, 26k stars), Changeset (udecode/plate, 17k stars) and Changeset (whitphx/stlite, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changeset PR?

module-federation (a GitHub organization) maintains it in module-federation/core, which has 2,655 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: module-federation/core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.