# Phatblat Dotfiles Commit Message > Ship Workflow - Skill: `tomevault-io/phatblat-dotfiles-commit-message` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/phatblat-dotfiles-commit-message` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/phatblat-dotfiles-commit-message/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/phatblat-dotfiles-commit-message --- # Ship Workflow ## Overview Complete shipping pipeline: review changes -> commit -> push -> PR (each step confirmed). ## Process ``` Phase 1: REVIEW -> git status + diff, understand all changes Phase 2: COMMIT -> Generate conventional commit message, confirm, commit Phase 3: PUSH -> Push to remote (if requested) Phase 4: PR -> Create PR with summary (if requested) ``` ## Phase 1: Review Changes Before generating a commit message: ```bash # 1. Check what's staged and untracked git status # 2. Review changes (staged + unstaged) git diff --cached git diff # 3. Check recent commit style git log --oneline -5 ``` ### Review Checklist - Are all intended files staged? - Are there files that should NOT be committed? (.env, large binaries, etc.) - Do changes make sense as a single commit or should they be split? ## Format (Conventional Commits) ``` ():