make-change-file
Create or update Remix repo change files under `packages/*/.changes`. Use when a user asks for release notes, a change file, a missing changelog entry, a prerelease note, or an update to existing unpublished release notes.
Best for Remix repository maintainersWorks with GitHubLow risk
⌘source
- author
@remix-run- repo
- remix-run/remix
- language
- TypeScript
★33kstars
2.8kforks
Apr 21, 2026
✦overview.md
Key Features
- ·Creates Remix-compatible change files
- ·Updates existing unpublished change files
- ·Follows repository-specific naming conventions
- ·Integrates with existing linting and preview workflows
- ·Determines appropriate version bump type
Use Cases
- →Adding missing changelog entries for recent changes
- →Creating prerelease notes for upcoming versions
- →Updating existing unpublished release notes
- →Generating release notes for new package releases
- →Maintaining consistent change file formatting across packages
Best for
- ✓Remix repository maintainers
- ✓Release engineering workflows
- ✓Teams using changesets for version management
Not ideal for
- !Non-Remix repositories
- !One-off documentation tasks
- !Projects without pnpm or changesets setup
FAQs
name
make-change-file
description
Create or update Remix repo change files under `packages/*/.changes`. Use when a user asks for release notes, a change file, a missing changelog entry, a prerelease note, or an update to existing unpublished release notes.
Make Change File
Overview
Write release notes that match this repository's .changes conventions. Use it for both new change files and edits to existing unpublished ones.
Workflow
- Read the package's
package.json,.changes/directory, and any relevant PR diff or commit range before writing anything. - Check whether an unpublished change file already exists for the same work. If it does, update it in place instead of creating a duplicate note.
- Choose the bump type from the package version and the user-facing impact.
- Write concise, user-facing release notes that describe shipped behavior, APIs, or exports.
- Run
pnpm changes:previewto verify the rendered changelog output. - Run
pnpm run lintbefore finishing.
Naming
- Use
packages/<package>/.changes/[major|minor|patch].short-description.md. - Keep the slug short, specific, and stable.
- Reuse existing deterministic names when the repo already has a pattern for that class of note.
- For Remix export-only changes, update
packages/remix/.changes/minor.remix.update-exports.mdin place. - For brand-new package releases, prefer
minor.initial-release.md.
Bump Rules
$install
1-click copynpx skills add remix-run/remix --skill make-change-fileSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.