القائمة
Commit changes in thematic groups with short messages that follow the repo's semantic conventions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when the user wants a download/adoption report for PaceBar releases — totals per operating system, per release, or a raw CSV of GitHub release download counts.
Use this skill when cutting a release — bumping or setting the PaceBar app version across all source-of-truth files (package.json, Cargo, tauri.conf, worker).
Use this skill when the user asks you to update outdated dependencies.
Migrate a project (single-app or monorepo) from any Vite version (4, 5, 6, 7, or rolldown-vite) to Vite 8 with Rolldown/Oxc. Covers discovery, intermediate upgrades, dependency bumps, config migration, build verification, and cleanup.
| name | do-commits |
| description | Commit changes in thematic groups with short messages that follow the repo's semantic conventions. |
Great! Now let's commit these changes in thematic groups with short messages that follow the repo's semantic conventions.
Use the format: type(scope): message
Types:
feat: New feature or componentfix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featurebuild: Changes to build system or dependencies (package.json, tsconfig, etc.)chore: Maintenance tasks (lockfile updates, etc.)docs: Documentation changestest: Adding or updating testsperf: Performance improvementsstyle: Code style changes (formatting, semicolons, etc.)Scope Examples:
contractsoxlint-config, tsconfig, dep-version-mapdeps, repo, ciMessage Guidelines:
Grouping Strategy:
Examples:
feat(contracts): add new user interface
refactor(oxlint-config): update react rules
build(tsconfig): enable strict mode
chore(deps): update pnpm lockfile
docs: update README with setup instructions