Git workflow
Git branching and commit message conventionsFrom its SKILL.md
npx -y skills add NinetrixAI/skills-hub --skill git-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.9 KB, 170 tokens by cl100k_base, as published. Nobody here has run it
Git Workflow
Branch naming
- Feature branches:
feat/<short-description> - Bug fixes:
fix/<short-description> - Chores:
chore/<short-description>
Commit messages
Use conventional commits: type(scope): description
Types: feat, fix, docs, style, refactor, test, chore
Examples:
feat(auth): add OAuth2 login flowfix(api): handle null response from upstream
Rules
- Never force-push to
mainormaster - Always create a branch for changes — never commit directly to main
- Keep commits atomic — one logical change per commit
- Write commit messages in imperative mood ("add feature" not "added feature")
- Rebase feature branches on main before merging
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.