// Generate commit messages following conventional commits with scope detection
| type | skill |
| name | Commit Message |
| description | Generate commit messages following conventional commits with scope detection |
| skillSlug | commit-message |
| phases | ["E","C"] |
| generated | "2026-03-02T00:00:00.000Z" |
| status | filled |
| scaffoldVersion | 2.0.0 |
Activate this skill when staging changes and preparing a git commit. It generates commit messages following Conventional Commits format with automatic scope detection based on the files changed.
git diff --staged to understand what was modified.apps/backend-express/ → scope: backend-expressapps/backend-nestjs/ → scope: backend-nestjsapps/frontend-nextjs/ → scope: frontend-nextjsapps/frontend-svelte/ → scope: frontend-sveltepackages/shared/ → scope: shared.context/ → scope: docsmonorepo or most relevant appfeat — New feature or capabilityfix — Bug fixrefactor — Code improvement without behavior changedocs — Documentation changestest — Adding or updating testschore — Build, config, or tooling changesstyle — Formatting, whitespace, missing semicolonstype(scope): short descriptionbackend-express, frontend-nextjs), the commit type should typically be fix (critical bug fixes only). If you find yourself writing feat for a legacy project scope, reconsider — new features belong in the active stack (NestJS/SvelteKit).feat(backend-nestjs): add pagination to franchise list endpoint
fix(frontend-nextjs): correct status filter on dashboard
refactor(shared): extract franchise row mapper utility
docs(docs): update architecture notes with data flow diagram
chore(monorepo): add Husky pre-commit hooks
test(backend-express): add integration tests for CRUD endpoints
Design RESTful APIs following best practices
Systematic bug investigation and root cause analysis
Review code quality, patterns, and best practices
Generate and update technical documentation
Break down features into implementable tasks
Review pull requests against team standards and best practices