Instruction file imported from ribeiroevandro/astro-base-template (.cursor/rules/commit-message.mdc). Copyright stays with the author.

Commit Message Conventions

Name: commit-message
Author: ribeiroevandro

All commits must follow the Conventional Commits format strictly:

Format: <type>[optional scope]: <gitmoji> <description>
Semantic types:
- feat (new feature, MINOR version bump)
- fix (bug fix, PATCH version bump)
- docs (documentation)
- style (formatting)
- refactor (code refactoring)
- perf (performance improvement)
- test (adding/refactoring tests)
- chore (maintenance/build)
- ci (CI/CD related changes)
Scope: Use a scope (e.g., login, notifications, payments) to describe the part of the codebase affected, when applicable.
Breaking changes: If a commit introduces a breaking change, add an exclamation mark (!) after the type/scope (e.g., feat(auth)!: remove old login API).
Description: Keep descriptions concise, imperative, and in the present tense (e.g., add, fix, refactor).
One task per commit: Each commit should represent a single task or change.

{ "ocm": "1", "id": "ribeiroevandro-astro-base-template-commit-message-rule", "kind": "skill", "name": "commit-message", "description": "All commits must follow the Conventional Commits format strictly:", "publisher": "ribeiroevandro", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "All commits must follow the Conventional Commits format strictly:" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/ribeiroevandro/astro-base-template", "path": ".cursor/rules/commit-message.mdc", "ref": "4b688ce7729abad783c55143c17dfe38d206667b", "url": "https://github.com/ribeiroevandro/astro-base-template/blob/4b688ce7729abad783c55143c17dfe38d206667b/.cursor/rules/commit-message.mdc", "key": "ribeiroevandro/astro-base-template/.cursor/rules/commit-message.mdc" } }, "instructions": "# Commit Message Conventions\n\nAll commits must follow the Conventional Commits format strictly:\n\n- **Format:** `<type>[optional scope]: <gitmoji> <description>`\n- **Semantic types:**\n - `feat` (new feature, MINOR version bump)\n - `fix` (bug fix, PATCH version bump)\n - `docs` (documentation)\n - `style` (formatting)\n - `refactor` (code refactoring)\n - `perf` (performance improvement)\n - `test` (adding/refactoring tests)\n - `chore` (maintenance/build)\n - `ci` (CI/CD related changes)\n- **Scope:** Use a scope (e.g., `login`, `notifications`, `payments`) to describe the part of the codebase", "cost": { "context_tokens": 246 } }

commit-message

About

Commit Message Conventions

Use it

Manifest

Reviews