Generate a Changeset file for the current branch using Shipfox agent automation. Trigger when the user asks to add a Changeset, document a change for release, bump versions, or prepare a PR that touches published packages.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Agents cannot drive the interactive pnpm exec changeset prompt. This skill
creates the equivalent .changeset/*.md file directly.
When a change may affect a published package, read the Changesets and publishing workflow. It owns when a Changeset is required, package eligibility, bump levels, and the shared summary rules.
Before writing the summary, read the repository writing guide. Apply its word, terminology, contraction, and sentence-length rules. Changeset summaries are published as release notes and are checked by the prose policy.
git diff origin/main...HEAD --name-only and apply the shared
workflow to decide whether a Changeset is required.package.json. Read
its name and private fields. Include only eligible published packages..changeset/ and write the
standard Changesets front matter with the selected package names and bumps.---
"@shipfox/api-runners": minor
---
Adds per-organization runner concurrency limits.
Use one front-matter entry per affected package.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
ALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.
The English summary is being prepared. Showing the original description.
Use when setting up a Shipfox workflow from a template.
The English summary is being prepared. Showing the original description.
Use when diagnosing a failed or stalled Shipfox workflow run, or an event that did not start one.
The English summary is being prepared. Showing the original description.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
The English summary is being prepared. Showing the original description.
ALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.
The English summary is being prepared. Showing the original description.
Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.
The English summary is being prepared. Showing the original description.