d4mp3-pathie-coding-practices-version-control-git-rule.ocm.json json {
"ocm": "1",
"id": "d4mp3-pathie-coding-practices-version-control-git-rule",
"kind": "skill",
"name": "coding-practices-version-control-git",
"description": "CODING_PRACTICES",
"publisher": "d4mp3",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"CODING_PRACTICES"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/d4mp3/Pathie",
"path": ".cursor/rules/coding-practices-version-control-git.mdc",
"ref": "3b7c38cb5870e2cf5fe1a5bb9c97698fe52c1bac",
"url": "https://github.com/d4mp3/Pathie/blob/3b7c38cb5870e2cf5fe1a5bb9c97698fe52c1bac/.cursor/rules/coding-practices-version-control-git.mdc",
"key": "d4mp3/Pathie/.cursor/rules/coding-practices-version-control-git.mdc"
}
},
"instructions": "## CODING_PRACTICES\n\n### Guidelines for VERSION_CONTROL\n\n#### GIT\n\n- Use conventional commits to create meaningful commit messages\n- Use feature branches with descriptive names following {{branch_naming_convention}}\n- Write meaningful commit messages that explain why changes were made, not just what\n- Keep commits focused on single logical changes to facilitate code review and bisection\n- Use interactive rebase to clean up history before merging feature branches\n- Leverage git hooks to enforce code quality checks before commits and pushes",
"cost": {
"context_tokens": 136
}
}
