generate-changeset

Estrellas13

Forks0

Actualizado22 de julio de 2026 a las 22:20

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

ShipfoxHQ

ShipfoxHQ/shipfox

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	generate-changeset
description	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.
allowed-tools	Read, Write, Bash, Glob, Grep

Generate Changeset

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.

Process

Inspect git diff origin/main...HEAD --name-only and apply the shared workflow to decide whether a Changeset is required.
For each changed package, walk upward to its nearest package.json. Read its name and private fields. Include only eligible published packages.
Apply the shared bump-level policy. If the change is breaking, explain the major-version impact and ask the user before writing it.
Generate an unused three-word filename under .changeset/ and write the standard Changesets front matter with the selected package names and bumps.
Write the summary using the shared workflow. Do not create a release pull request or run the publisher.
Report the filename, package bumps, and summary. The calling workflow is responsible for committing the file with the implementation.

File shape

---
"@shipfox/api-runners": minor
---

Adds per-organization runner concurrency limits.

Use one front-matter entry per affected package.

Más de este repositorio

mismo repositorio

ShipfoxHQ/shipfox

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.

2026-07-2313

commit

ShipfoxHQ/shipfox

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.

2026-07-2213

readme-writer

ShipfoxHQ/shipfox

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 runs the repository readability check. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.

2026-07-2213

name	generate-changeset
description	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.
allowed-tools	Read, Write, Bash, Glob, Grep

Generate Changeset

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.

Process

Inspect git diff origin/main...HEAD --name-only and apply the shared workflow to decide whether a Changeset is required.
For each changed package, walk upward to its nearest package.json. Read its name and private fields. Include only eligible published packages.
Apply the shared bump-level policy. If the change is breaking, explain the major-version impact and ask the user before writing it.
Generate an unused three-word filename under .changeset/ and write the standard Changesets front matter with the selected package names and bumps.
Write the summary using the shared workflow. Do not create a release pull request or run the publisher.
Report the filename, package bumps, and summary. The calling workflow is responsible for committing the file with the implementation.

File shape

---
"@shipfox/api-runners": minor
---

Adds per-organization runner concurrency limits.

Use one front-matter entry per affected package.