// Generate a changeset file describing the current PR's changes. Use when asked to "create a changeset", "add a changeset", "/changeset", or after implementing a feature/fix that needs a changelog entry. Produces a randomly named `.changeset/*.md` file with affected packages, bump type, and an 80-character-max user-facing summary.
| name | changeset |
| description | Generate a changeset file describing the current PR's changes. Use when asked to "create a changeset", "add a changeset", "/changeset", or after implementing a feature/fix that needs a changelog entry. Produces a randomly named `.changeset/*.md` file with affected packages, bump type, and an 80-character-max user-facing summary. |
| disable-model-invocation | true |
Generate a properly formatted changeset file in .changeset/ describing the work on the current branch / PR. Follow the project's changeset conventions in .cursor/rules/090-changesets.mdc.
Determine what changed on the current branch versus the default branch:
echo "=== BRANCH ===" && git rev-parse --abbrev-ref HEAD && echo "=== CHANGED FILES ===" && git diff --name-only origin/main...HEAD && echo "=== DIFF SUMMARY ===" && git diff --stat origin/main...HEAD
If origin/main is not available, fall back to staged + unstaged changes (git status and git diff).
Create one for: new features, bug fixes, breaking changes, performance improvements, security fixes.
Skip for: refactors with no user impact, formatting, docs-only, tests-only, internal tooling, dev dependency bumps.
If a changeset is not needed, tell the user and stop.
Map changed file paths to package names from package.json files. Common mappings:
| Path | Package name |
|---|---|
apps/api/** | @deadlock-mods/api |
apps/bot/** | @deadlock-mods/bot |
apps/desktop/** | @deadlock-mods/desktop |
apps/lockdex/** | @deadlock-mods/lockdex |
apps/www/** | @deadlock-mods/www |
packages/common/** | @deadlock-mods/common |
packages/database/** | @deadlock-mods/database |
packages/shared/** | @deadlock-mods/shared |
packages/ui/** | @deadlock-mods/ui |
packages/<name>/** | @deadlock-mods/<name> |
Only include packages directly modified. Do not include transitive dependents.
| Type | When |
|---|---|
patch | Bug fixes, small internal-facing changes with user impact |
minor | New features, backwards-compatible additions |
major | Breaking changes that require user action |
Pick a random kebab-case filename matching the existing convention adjective-noun-verb.md (three short words, lowercase, hyphen-separated).
Examples already in .changeset/: swift-foxes-leap.md, gentle-cats-gather.md, brave-otters-fall.md.
Verify the filename does not already exist in .changeset/ before writing. If it collides, pick another.
Write to .changeset/<random-name>.md using this exact format:
---
"@deadlock-mods/<package>": <patch|minor|major>
---
<Summary, max 80 characters, starts with a verb, user-facing>
For multiple affected packages, list each on its own line in the frontmatter.
Summary rules:
Add, Fix, Improve, Remove, Update)Good summaries:
Add dark mode toggle to settings page
Fix crash when downloading large mod files
Improve mod installation performance by 50%
Bad summaries:
Updated code
Fixed bug
Refactored component
chore: refactor download logic to use streams (over 80 chars and not user-facing)
Print the path to the created file and its contents. Do not stage or commit it unless asked — it will be committed alongside the user's code changes.
Created .changeset/brave-foxes-hunt.md:
---
"@deadlock-mods/desktop": patch
---
Fix crash when launching the game after disabling all mods
User: "/changeset", "create a changeset", or "add a changeset for this PR"
Response:
Version Bump
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.
Find deepening opportunities in a codebase, informed by the architecture docs in apps/docs/content/docs/developer-docs/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Split React/TSX files containing multiple inlined components into separate single-responsibility files. Use when asked to "split components", "extract components", "single responsibility", "clean up component file", "too many components in one file", "component slop", or when running deslop/cleanup on React code.