// Review the latest changelog entry in packages/blog/changelog.ts against the project's changelog style guide and flag bullets that need rewriting. Use when checking a freshly added changelog entry before opening a PR, or when the user asks to review/lint the latest changelog.
Convert a page to the cross-platform page system so it works in both the website and the desktop app. Use when moving a page into packages/ui/src/layouts/, creating shared or wrapped layouts, or setting up DI contracts for platform abstraction.
Add a new API endpoint module to packages/api-client from an OpenAPI schema. Use when adding new backend endpoints, creating API client modules, or when an openapi.yml is provided.
Use the Figma MCP server to translate a Figma design into a Vue page or component layout. Use when the user provides a Figma URL, asks to implement a design, or wants to draft a page layout from Figma.
Perform an i18n localization pass on changed files or a pull request, converting hard-coded English strings to the @modrinth/ui i18n system. Use when internationalizing a set of changes, reviewing a PR for untranslated strings, or converting a specific component.
Convert a page or component from useAsyncData/manual ref patterns to TanStack Query for server state management. Use when migrating data fetching to useQuery/useMutation, adding cache invalidation, or replacing useAsyncData with TanStack Query.
| name | review-changelog |
| description | Review the latest changelog entry in packages/blog/changelog.ts against the project's changelog style guide and flag bullets that need rewriting. Use when checking a freshly added changelog entry before opening a PR, or when the user asks to review/lint the latest changelog. |
| argument-hint | ["product?"] |
Refer to the standard: @standards/maintaining/CHANGELOG.md
Locate the latest entry:
packages/blog/changelog.ts.VERSIONS array.$ARGUMENTS specifies a product (web, hosting, app), review the most recent entry for that product. Otherwise, review the most recent entry overall, plus any sibling entries sharing the same date (coordinated releases ship together).Read the standard above in full before reviewing. The bullet rules, section/verb agreement, and "Don't" list are the source of truth.
Check the entry shell:
date is a valid ISO 8601 timestamp.product is one of web, hosting, app.version is present for app entries and omitted for web/hosting.## Added, ## Changed, ## Fixed, ## Security (or a featured-release linked heading). Flag legacy ## Improvements.Review each bullet against the standard. For each bullet, check:
Report findings as a short list grouped by entry. For each problem bullet, show the original line and a suggested rewrite. If the entry is clean, say so explicitly. Do not edit the file unless the user asks - this skill is a review pass, not a rewrite pass.
If the user then asks to apply fixes, edit packages/blog/changelog.ts directly using the suggested rewrites. Preserve tab indentation and template literal formatting.