<h1 align="center">
<a href="https://prompts.chat">
The user will issue this command. You will need to do two things.
Sign in to like and favorite skills
The user will issue this command. You will need to do two things.
Create a changeset using the CLI. The CLI will automatically detect changed packages and create the changeset file.
pnpm changeset -s -m "your changeset message" [--major pkg1] [--minor pkg2] [--patch pkg3]
Arguments:
-s or --skipPrompt - Run non-interactively (required for automation)-m "message" or --message "message" - The changeset message (required)--major @scope/pkg - Packages that should have a major version bump--minor @scope/pkg - Packages that should have a minor version bump--patch @scope/pkg - Packages that should have a patch version bump (default for detected changes)Version bump types:
patch - Bugfixes with backward-compatible changesminor - New features with backward-compatible changesmajor - Breaking changes that are not backward-compatibleMessage guidelines:
Use gh cli to open a PR for the current branch in the user's browser. Do not open it directly, use the web option that opens it in the browser so the user can edit the title/description if needed.
Add a descriptive/concise title, use conventional commits in the title (e.g. "fix: title here" or "feat(pkg-name): title here").
Add a concise, humble PR description without flowery or overly verbose language. Keep it casual/friendly but get to the point. Show simple code examples before/after for fixes, or just after examples for new features. Do not add lists or headings. Keep it simple and to the point.