Create or update Remix repo change files under packages/*/.changes.
npx skills add https://github.com/remix-run/remix --skill make-change-file
Please help me install this Agent Skill. Skill: make-change-file Source: https://github.com/remix-run/remix/tree/main/.agents/skills/make-change-file Command: npx skills add https://github.com/remix-run/remix --skill 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.
Centralizes and standardizes release notes by generating or updating package change files to align with the repo's conventions, reducing manual effort and ensuring consistency across releases.
Create or update a package's change file under packages/*/.changes with a concise, user-facing note describing the release.
High-intent search queries and answers about installing and using this skill.
To create release notes for Remix packages, you generate or update change files under packages/*/.changes. This standardizes entries into concise, user-facing notes describing shipped behavior, APIs, or exports.
To update unpublished change files without duplicates, the system detects existing notes under packages/*/.changes and updates them in place. This prevents redundant entries while maintaining repo conventions.
A change file determines the correct bump type by analyzing the targeted package changes and user input. It enforces the appropriate version bump—major, minor, or patch—based on repository conventions.
Package change files are validated by checking formatting and content against repository-specific lint rules. This ensures the output is a ready-to-render changelog entry that aligns with repo standards.
You generate a prerelease note or changelog entry when a user requests release notes, a missing changelog entry, or updates to existing unpublished release notes. This centralizes and standardizes the documentation process.
involvexIdentify required and optional codebase files for answering developer questions.
AutumnsGroveSwaps registry to npm for publishing, then reverts to avoid conflicts.
actionbookStandardize Rust naming, formatting, and linting conventions across codebases.
gewoonsebaAutomate Git commit, push, and pull request creation via gh.
