Skip to content

ShipfoxHQ/shipfox / .agents/skills/generate-changeset

generate-changeset

Verified

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.

FileKindSize
SKILL.mdskill md2.0 KB
---
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](../../../docs/guides/local-development-and-release-workflow.md#publish-packages-with-changesets).
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](../../../WRITING.md).
Apply its word, terminology, contraction, and sentence-length rules. Changeset
summaries are published as release notes and are checked by the prose policy.

## Process

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

## File shape

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

Adds per-organization runner concurrency limits.
```

Use one front-matter entry per affected package.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall