# J4flmao Agent Skills Git Workflow > Git Workflow - Skill: `tomevault-io/j4flmao-agent-skills-git-workflow` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/j4flmao-agent-skills-git-workflow` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/j4flmao-agent-skills-git-workflow/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/j4flmao-agent-skills-git-workflow --- # Git Workflow ## Purpose Establish consistent git conventions for commit messages, branching, and pull requests. ## Agent Protocol ### Trigger Exact user phrases: "commit message", "branch name", "git workflow", "PR template", "conventional commits", "git strategy", "merge vs rebase", "release workflow". ### Input Context Before activating, verify: - The context is known (new commit, new branch, PR, or release). - The project's git conventions or lack thereof is understood. - The user's intent (what they want to do with git) is clear. ### Output Artifact No file output. This skill produces git commands or templates. ### Response Format Git command sequence or conventional commit template. No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. No explanation of why git conventions matter. ### Completion Criteria This skill is complete when: - [ ] The correct git command or commit message template is produced. - [ ] The response follows conventional commits format if applicable. - [ ] Branch naming follows the project convention. - [ ] Merge strategy is specified if asked. ### Max Response Length 15 lines. ## Quick Start Conventional commits: `(): `. Branch: `/-`. One concern per PR. ## When to Use This Skill - Writing commit messages - Creating branches - Reviewing PR conventions - Setting up release workflow - Onboarding team to git conventions ## Core Workflow ### Step 1: Conventional Commits ``` ():