# Git Commit Pr

> INVOKE BEFORE any git commit, PR creation, or Graphite CLI (gt) operation. Covers gt commands, commit best practices, error fixes, and gh view-md usage.

- Skill: `majiayu000/git-commit-pr` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/git-commit-pr`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/git-commit-pr/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/git-commit-pr

---


# Git, GitHub & Graphite Workflow

## Commit Message Best Practices

1. **Focus on the "why", not the "what"**: Explain the motivation and benefits of the change rather than describing what was changed
2. **Highlight security implications**: If the change prevents vulnerabilities or security issues, state this clearly
3. **Describe behavior changes**: Explain how the API/behavior changes from the developer's perspective
4. **Use active voice**: "Make X do Y" rather than "X was changed to Y"

## Graphite CLI Commands

### Viewing Stack Status
- `gt log` - Show the current stack structure with PRs and commits
- `gt log --short` - Compact view of the stack

### Creating Commits and Branches
- `git add <files> && gt create -m "message"` - Stage specific files, then create branch
- `gt create -a -m "message"` - Stage ALL changes (including untracked) and create new branch
- `gt create -u -m "message"` - Stage only tracked file updates and create new branch
- `gt modify` - Amend current commit
- `gt modify -a` - Stage all changes and amend
- `gt modify -c -m "message"` - Create new commit instead of amending

### Syncing and Rebasing
- `gt get` - Sync current stack from remote; use when encountering stale trunk or merged PR issues (only affects current stack, not others)
- `gt move --onto main` - Rebase current branch onto main/trunk
- `gt track --parent main` - Re-parent branch to track main directly (when branch was stacked on now-merged PRs)
- `gt restack` - Rebase branch onto its parent; use `--only` for just current branch

### Submitting PRs
- `gt submit --no-edit` - Push and create/update PR; uses commit message as PR title/description
- `gt submit --no-edit -s` - Submit entire stack (current branch + descendants)
- `gt submit --no-edit --draft` - Create PR in draft mode
- `gt submit --no-edit --publish` - Publish draft PRs
- `gt submit --no-edit --reviewers "user1,user2"` - Set reviewers

### Common Error Fixes
| Error | Solution |
|-------|----------|
| "PRs have already been merged or closed" | Run `gt get` first |
| "Aborting submit due to out of date trunk" | Run `gt get` to update trunk |
| Branch stacked on merged PR | `gt track --parent main` then `gt restack --only` |

### PR Workflow: Submit Then Configure

1. **Submit PR** (creates in draft mode when using `--no-edit`):
   ```bash
   gt submit --no-edit
   ```

2. **Update PR description** using GitHub API:
   ```bash
   gh api repos/{owner}/{repo}/pulls/{number} -X PATCH -f title="Title" -f body="$(cat <<'EOF'
   ## Summary
   - Change 1
   - Change 2

   ## Test plan
   - [ ] Test item
   EOF
   )"
   ```

3. **Mark ready for review**:
   ```bash
   gh pr ready {number} -R {owner}/{repo}
   ```

## Reading GitHub Issues and PRs

- **ALWAYS use `gh view-md <github-issue-or-pr-url>`** when given a GitHub URL
- Returns a well-formatted markdown summary with all necessary information
- Works for both issues and pull requests

## PR Description Guidelines

Write a concise PR description that:
- Explains why the change is needed
- Answers likely reviewer questions
- Does NOT summarize the diff
- Includes only essential context (rationale, safety/tests/rollback) when relevant