git-workflow
starsforks
How to install git-workflow?
omnigentx/jarvis/git-workflow
$npx -y skills add omnigentx/jarvis --skill git-workflowGit workflow and conventions. Use when a Dev or DSO needs to commit, branch, or open a pull request following the team standard.
SKILL.md
| 1 | # GIT WORKFLOW |
| 2 | |
| 3 | ## Branch strategy |
| 4 | |
| 5 | ``` |
| 6 | main (production) |
| 7 | ├── develop (staging) |
| 8 | │ ├── feature/add-dark-mode |
| 9 | │ ├── feature/new-agent-card |
| 10 | │ ├── bugfix/fix-calendar-dup |
| 11 | │ └── hotfix/fix-auth-crash |
| 12 | ``` |
| 13 | |
| 14 | ## Branch naming |
| 15 | - `feature/<short-description>` — new feature |
| 16 | - `bugfix/<short-description>` — bug fix |
| 17 | - `hotfix/<short-description>` — urgent prod fix |
| 18 | |
| 19 | ## Commit conventions |
| 20 | |
| 21 | ``` |
| 22 | <type>(<scope>): <description> |
| 23 | |
| 24 | Types: feat, fix, docs, refactor, test, chore |
| 25 | Scope: backend, frontend, skills, infra |
| 26 | ``` |
| 27 | |
| 28 | Examples: |
| 29 | - `feat(backend): add finance decision tree skill` |
| 30 | - `fix(frontend): fix agent card overflow on mobile` |
| 31 | - `refactor(skills): merge system-design into architecture` |
| 32 | |
| 33 | ## Pull request template |
| 34 | |
| 35 | ```markdown |
| 36 | ## What |
| 37 | [Short description] |
| 38 | |
| 39 | ## Why |
| 40 | [Reason for the change] |
| 41 | |
| 42 | ## How |
| 43 | [Approach / technical details] |
| 44 | |
| 45 | ## Testing |
| 46 | - [ ] Unit tests pass |
| 47 | - [ ] Manual testing done |
| 48 | |
| 49 | ## Screenshots (if UI) |
| 50 | ``` |
| 51 | |
| 52 | ## Rules |
| 53 | - Commit often, with clear messages. |
| 54 | - One PR = one feature or bug fix. |
| 55 | - Rebase before merging (no merge commits). |
| 56 | - DO NOT push directly to main. |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
