Back to skills
SkillHub ClubShip Full StackFull Stack
commit-convention
Conventional commit message format and rules for this project
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
238
Hot score
98
Updated
March 20, 2026
Overall rating
C3.2
Composite score
3.2
Best-practice grade
B84.0
Install command
npx @skill-hub/cli install spirimirror-libuipc-commit-convention
Repository
spiriMirror/libuipc
Skill path: .cursor/skills/commit-convention
Conventional commit message format and rules for this project
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: spiriMirror.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install commit-convention into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/spiriMirror/libuipc before adding commit-convention to shared team environments
- Use commit-convention for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: commit-convention description: Conventional commit message format and rules for this project --- # Commit Convention Use [Conventional Commits](https://www.conventionalcommits.org/) format: ``` <type>(<scope>): <short summary> ``` ## Types | Type | When to Use | |---|---| | `feat` | New feature | | `fix` | Bug fix | | `refactor` | Code restructuring (no behavior change) | | `perf` | Performance improvement | | `test` | Adding or updating tests | | `docs` | Documentation only | | `build` | Build system or dependency changes | | `ci` | CI/CD changes | | `chore` | Other maintenance tasks | ## Examples ``` feat(geometry): add label_open_edge utility fix(cuda): resolve race condition in contact solver refactor(core): simplify scene validation logic test(sim_case): add ABD-FEM contact test docs: update build instructions ``` ## Rules - **Scope** is optional but encouraged — use the module name (e.g., `geometry`, `core`, `cuda`, `io`). - **Summary** should be lowercase, imperative mood, no period at the end. - Add a blank line then a body for longer explanations if needed. - Reference issues with `Fixes #<number>` or `Closes #<number>` in the body.