commit-convention
Skill351 starsChanged 3 months agoApache-2.0View on GitHub
Conventional commit message format and rules for this project
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kana-consultant/kana-best-practice-engineeringtheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kana-consultant/kana-best-practice-engineering★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cpp-format.mdcCursor rule
- .cursor/rules/self-improvement.mdcCursor rule
- cmake-workflowSkill
- commitSkill
- cursor-rulesSkill
- documentSkill
- fix-issueSkill
- fix-prSkill
- formatSkill
- github-prSkill
- gpu-optimizationSkill
- project-structureSkill
- push-tagSkill
- repository-setupSkill
- review-prSkill
- run-testsSkill
- simulation-devSkill
- xmake-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use Conventional Commits format:
- Distinctive: line 41
Summary: should be lowercase, imperative mood, no period at the end.
- Distinctive: line 42
Add a blank line then a body for longer explanations if needed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit Convention
Use Conventional Commits 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 instructionsRules
- 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>orCloses #<number>in the body.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.