菜单
Update all dependencies to latest minor versions across the Mantine monorepo, validate, test, build, and generate a report. Use when the user wants to update dependencies, upgrade packages, run dependency maintenance, or asks to "update deps", "upgrade dependencies", "dependency update", "/update-dependencies".
Research new features shipped by other React and Vue component libraries over a given time period and compare them against Mantine to find gaps and divergences. Use when the user wants competitive analysis of UI libraries, to track what competitors added recently, to find missing Mantine features, or asks things like "what did MUI/Chakra/Ant add since X", "what features are we missing", "compare our components to competitors", "feature gap analysis". Operates from the Mantine monorepo.
Merge changes down the release branch chain (master → 9.0 → 9.1 → … → 9.X). Resolves merge conflicts, pushes to the correct remote per branch. Use when the user wants to cascade/propagate changes from master through all minor release branches (e.g., "merge cascade", "propagate master", "cascade merge", "/merge-cascade").
Run an automated code review of unstaged changes using Codex CLI, then fix issues and re-review in a loop until approved. Use when the user asks to review changes with Codex, run a code review cycle, or invokes /codex-code-review.
Initialize a new Mantine minor or major release: creates a git branch, sets up the changelog MDX page, updates mdx-meta-data.ts, mdx-nav-data.ts, and versions.ts, and commits. Use when the user wants to start a new release (e.g., "new release 9.1.0", "/new-mantine-release 9.1.0", "initialize 9.2.0 release").
Sync Mantine GitHub releases into packages/@mantinex/mantine-meta/src/versions.ts. Use when the user wants to update the versions list, sync release dates, add missing patch versions, or update changelog links for older major versions. Triggers on requests like "sync versions", "update versions.ts", "add missing releases".
| name | update-dependencies |
| description | Update all dependencies to latest minor versions across the Mantine monorepo, validate, test, build, and generate a report. Use when the user wants to update dependencies, upgrade packages, run dependency maintenance, or asks to "update deps", "upgrade dependencies", "dependency update", "/update-dependencies". |
Update all dependencies to their latest minor versions, validate everything works, and produce a report.
Run npx npm-check-updates to update all package.json files to latest minor versions:
npx npm-check-updates --target minor -u --deep
npm run syncpack:fix
npm run syncpack:format
yarn install
If npm run syncpack (list-mismatches) still reports errors after fix, resolve them manually.
npm run test:all
This runs oxfmt, syncpack, typecheck, lint, and jest.
If there are formatting/lint errors, fix them:
npm run format:write
npx eslint --fix packages apps/mantine.dev/src apps/help.mantine.dev/src scripts --cache
If there are type errors caused by updated packages (e.g., recharts changing generic type parameters), fix them with minimal changes — use type assertions or add missing type arguments. These are minor fixable errors.
Re-run npm run test:all to confirm fixes. If there are major errors that require significant refactoring, document them in the report but do not attempt large refactors.
npm run build all
Verify no build errors. If there are errors, document them in the report.
npm run storybook
Wait for Storybook to start (watch for "Storybook X.X started" or the local URL in output). Verify it starts without crash. Kill the process after confirming. Document any errors in the report.
npm run docs:build
Verify it completes without errors. Document any errors in the report.
Run ncu without -u to list available major updates (for the report only, do not install):
npx npm-check-updates --deep
Filter the output to show only major version bumps (where the major version number changed).
Create claude/{YYYY-month-DD}-dependencies-update.md where month is lowercase full name (e.g., 2026-march-08-dependencies-update.md).
Report format:
# Dependencies Update — YYYY-MM-DD
## Updated packages (minor)
| Package | From | To |
|---------|------|----|
| package-name | 1.2.3 | 1.3.0 |
| ... | ... | ... |
## Validation results
- **syncpack**: PASS/FAIL (details if fail)
- **test:all**: PASS/FAIL (details if fail)
- **build**: PASS/FAIL (details if fail)
- **storybook**: PASS/FAIL (details if fail)
- **docs:build**: PASS/FAIL (details if fail)
## Errors encountered
(List any errors that were fixed or remain unresolved)
## Available major updates (not installed)
| Package | Current | Latest | Notes |
|---------|---------|--------|-------|
| package-name | 1.x | 2.x | |
| ... | ... | ... | |
If all validations pass (or only minor fixable issues were resolved), create a commit:
[core] Update minor dependencies version
Stage all changed package.json files, yarn.lock, and any files modified to fix minor errors.
If there are unresolved major errors, do NOT commit — only generate the report.