Git Workflow
SkillDev toolsStructured git workflow for commits, branches, and PRs. Use when the user says "commit", "create a PR", "new branch", "prepare for review", "ship this", or "push my changes". Safe, conventional git operations with checkpoints.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Git Workflow skill
What this skill tells your AI
The instructions your AI receives, as published by mfielding92/clawedback in .claude/skills/git-workflow/SKILL.md and read by ahel’s review.
Safe, structured git operations with user checkpoints before irreversible actions.
Goal
Ensure git operations are safe, conventional, and reviewable.
- Commit done: user-approved commit exists with conventional message and hash returned
- Branch done: correctly named branch created and checked out, confirmed to user
- PR done: branch pushed, PR created via
gh, PR URL returned to user
Dependencies
Tools: Bash (all git operations, gh CLI for PRs)
CLI required: git (always available), gh (GitHub CLI — required for PR command only; warn user if not installed)
No MCP or external API required
Context
- Read
CLAUDE.mdfor project-specific branch naming conventions before creating a branch - Check
.github/pull_request_template.mdbefore drafting a PR body; use it as the template if present - Check
.github/CODEOWNERSor CI config if relevant for reviewer assignment
Commands
Commit: /git-workflow commit [message]
- Run
git statusandgit diff --stagedto understand changes - Check for sensitive files (.env, credentials, secrets) — WARN and exclude if found
- Determine which files to stage (never
git add -Aorgit add .— stage specific files) - If no message provided, draft one:
- Prefix: feat/fix/refactor/docs/test/chore
- Focus on WHY, not WHAT (the diff shows what)
- Under 72 chars for subject line
CHECKPOINT: Present staged file list and draft commit message. Do NOT commit until user approves.
- Create the commit
Branch: /git-workflow branch [name]
- Run
git status— warn if uncommitted changes exist; ask user to commit or stash before proceeding - Fetch latest from remote (
git fetch) - Derive branch name: use provided name or propose one from context using convention
feat/description,fix/description,refactor/description
CHECKPOINT: Show proposed branch name and source branch (e.g., main). Do NOT create the branch until user approves.
- Create branch from main/master and switch to it
- Output: "Created and switched to
branch-namefrommain."
PR: /git-workflow pr
- Run
git status— warn if uncommitted changes - Run
git log main..HEADto understand all commits on this branch - Run
git diff main...HEADfor the complete diff - Draft PR with:
- Short title (under 70 chars)
- Summary section with 1-3 bullet points
- Test plan checklist
CHECKPOINT: Show PR title, summary, and test plan. Do NOT push or create PR until user confirms.
- Push branch with
-uflag if not pushed - Create PR via
gh pr create - Return the PR URL
Output
- Commit: confirmation message with hash
- Branch: confirmation with branch name
- PR: the PR URL
Safety Rules
- NEVER force push to main/master
- NEVER commit .env, credentials, API keys, tokens
- NEVER amend published commits without explicit request
- NEVER skip pre-commit hooks (--no-verify)
- Always stage specific files, not everything
- Always verify branch before pushing
Signals
- GitHub stars
- 23
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
git-workflow-mfielding92- Source
- github.com/mfielding92/clawedback