Git Workflow
- 2 installs
- 512 repo stars
- Updated February 11, 2026
- meleantonio/chernycode
Defines a GitHub Flow branching strategy and Conventional Commits conventions for committing code, branching, and pull requests.
About
Prescribes GitHub Flow branching, Conventional Commit prefixes, atomic commit best practices, and a pre-commit checklist. A developer uses it when committing code, creating branches, or opening pull requests.
- GitHub Flow with descriptive feature/fix branch names
- Conventional Commits table with prefixes and examples
Git Workflow by the numbers
- 2 all-time installs (skills.sh)
- Ranked #497 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/meleantonio/chernycode --skill git-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 512 |
| Last updated | February 11, 2026 |
| Repository | meleantonio/chernycode ↗ |
What it does
Defines a GitHub Flow branching strategy and Conventional Commits conventions for committing code, branching, and pull requests.
Files
Git Workflow
Branch Strategy
- Use GitHub Flow
- Main branch is always deployable
- Create feature branches from main
- Use descriptive branch names:
feature/add-auth,fix/login-bug
Conventional Commits
Use the following prefixes:
| Prefix | Description |
|---|---|
feat: | New feature |
fix: | Bug fix |
docs: | Documentation only |
style: | Formatting, no code change |
refactor: | Code change without feature/fix |
test: | Adding or updating tests |
chore: | Maintenance, dependencies |
Examples:
feat: add user authentication endpoint
fix: resolve login timeout issue
docs: update API documentation
refactor: extract validation logic to utility
test: add unit tests for auth service
chore: update dependenciesCommit Best Practices
- Write clear, concise messages
- Focus on "why" not "what"
- Keep commits atomic (one logical change)
- Run tests before committing
- Never commit secrets or credentials
Pre-Commit Checklist
1. Run tests: pytest 2. Format code: ruff format . 3. Lint code: ruff check . 4. Review changes: git diff
Pull Requests
- Create descriptive PR titles
- Include summary of changes
- Reference related issues
- Request reviews from relevant team members
Files to Never Commit
.envfiles with secretscredentials.json- API keys or tokens
- Large binary files
- IDE-specific files (unless shared team config)
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148