← ClaudeAtlas

pmo-git-pushlisted

Prepare commit message with proper traceability, format git commands, track changes to origin (push workflow for PMO projects)
witchwasin/Axiom-PMO · ★ 3 · Code & Development · score 74
Install: claude install-skill witchwasin/Axiom-PMO
# PMO Skill: Git Push & Commit Workflow > **Trigger words:** push to origin, git push, commit and push, stage files, submit to git, send to origin, ready to push > **Related Skills:** pmo-traceability (Activity/Decision/Change Log), pmo-taskboard (card status tracking) > **Key Output:** Formatted commit message + git commands + traceability logging --- ## Before You Push: Pre-Flight Checklist ### 1. Verify Traceability Logging Before committing, ensure `P{XX}-{CODE}/SystemFlow/REQ_Traceability_Matrix.md` contains: - ✅ **Change Log entry** — what files changed, when, why, status - ✅ **Activity Log entry** — AI actions (Created/Updated/Merged/Validated) - ✅ **Decision Log entry** — any decisions made during work - ✅ **Session ID** — which Claude session number (S001, S005, etc.) ### 2. File Status Check ```bash git status ``` Expected output shows: - **Staged changes** (green) — files marked for commit - **Untracked files** (red) — new files not yet added - **Modified files** (red) — changed files not yet staged ### 3. Review Changed Files ```bash git diff --cached ``` Verify all changes are intentional before committing. --- ## Commit Message Format ### Template Structure ``` [PROJECT] TYPE: Brief description [Ref: MOM#X[-] Topic] Detailed Body: - What changed (file list / feature / fix) - Why changed (requirement / feedback / issue) - How changed (approach / method / validation) - Impact (modules / workflows / scope affected) Traceability: - Session: S{NNN} (Clau