Enforce project-specific Git commit message conventions compatible with commitlint and pre-commit hooks. Use this skill whenever the user asks to write a commit message, create a git commit, stage and commit changes, suggest a commit for their changes, or review/fix an existing commit message. Also trigger when the user says "commitea esto", "hazme un commit", "qué mensaje de commit uso", or any variation of committing code changes.
This project enforces strict commit message rules validated by commitlint and a custom pre-commit hook. Every commit message must pass both checks or the commit will be aborted.
<type>(<scope>): <description>
<scope> is optional but recommended<description> starts after the colon + space| Type | Use for |
|---|---|
feat | New feature or capability |
fix | Bug fix |
chore | Maintenance tasks, dependency updates, config |
docs | Documentation only changes |
test | Adding or updating tests |
style | Formatting, missing semicolons (no logic change) |
refactor | Code restructuring without behavior change |
perf | Performance improvements |
build | Build system or tooling changes |
ci | CI/CD pipeline changes |
revert | Reverting a previous commit |
^(feat|fix|chore|docs|test|style|refactor|perf|build|ci|revert)(\(.+?\))?: .{1,}$
feat(auth): add JWT refresh token rotation
fix(api): handle null response from payment gateway
chore(deps): upgrade vite to 5.4.0
docs(readme): update local setup instructions
test(cart): add edge cases for empty cart checkout
refactor(user): extract profile validation to separate module
perf(images): lazy load hero images on landing page
build(docker): optimize multi-stage build layers
ci(github): add job to run e2e tests on PR
style(button): fix inconsistent spacing in component