Git Workflow

Git Workflow

Guided workflows for common git operations that benefit from structured steps.

PR Preparation

When preparing a pull request:

1. Gather context

• git log main..HEAD --oneline — list all commits on the branch
• git diff main...HEAD --stat — see all changed files
• git status — check for uncommitted work

1. Draft PR content

• Title: under 70 chars, describes the change (not the branch name)
• Body: summarise the "why", list key changes, add test plan
• Use the commit history to write the summary — don't rely on memory

1. Push and create

``bash git push -u origin HEAD gh pr create --title "..." --body "$(cat /tmp/extracted.txt

• Apply changes manually to main
• Close original PR with explanation

1. Verify — run tests, check the diff looks right

Monorepo Release Tags

In monorepos, scope tags to the package:

# ❌ Ambiguous in monorepos
git tag v2.1.0

# ✅ Scoped to package
git tag contextbricks-v2.1.0
git push origin contextbricks-v2.1.0

Pattern: {package-name}-v{semver}

.gitignore-First Init

When creating a new repo, always create .gitignore BEFORE the first git add:

cat > .gitignore << 'EOF'
node_modules/
.wrangler/
dist/
.dev.vars
*.log
.DS_Store
.env
.env.local
EOF

git init && git add . && git commit -m "Initial commit"

If node_modules is already tracked:

git rm -r --cached node_modules/
git commit -m "Remove node_modules from tracking"

Private Repo License Audit

Before publishing or sharing a private repo:

gh repo view --json visibility -q '.visibility'

If PRIVATE, ensure:

• LICENSE contains proprietary notice (not MIT/Apache)
• package.json has "license": "UNLICENSED" and "private": true
• No CONTRIBUTING.md or "contributions welcome" in README

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: jezweb
• Source: jezweb/claude-skills
• License: MIT
• Homepage: https://jezweb.com.au

Install and usage instructions live in the source repository linked above.