brycewang-stanford/Auto-Empirical-Research-Skills / skills/14-luischanci-claude-code-research-starter/dot-claude/skills/commit
commit
VerifiedStage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
SKILL.md
View on GitHub---
name: commit
description: Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.
disable-model-invocation: true
argument-hint: "[optional: commit message]"
allowed-tools: ["Bash", "Read", "Glob"]
---
## Commit Workflow
Perform the full commit-PR-merge cycle.
### Steps
1. **Check current state**:
```bash
git status
git diff --stat
git log --oneline -5
```
2. **Create branch**: `git checkout -b [descriptive-branch-name]`
3. **Stage files**:
- Stage specific files (never `git add -A`)
- Exclude: `settings.local.json`, `.env`, credentials, large data files
- Review what's being staged
4. **Commit**:
- Use `$ARGUMENTS` as commit message if provided
- Otherwise, analyze changes and write a descriptive message
- Format: imperative mood, concise, explains WHY not WHAT
5. **Push and create PR**:
```bash
git push -u origin [branch-name]
gh pr create --title "[message]" --body "[summary of changes]"
```
6. **Merge** (with user approval):
```bash
gh pr merge --merge --delete-branch
git checkout main
git pull
```
### Important
- Never commit directly to main
- Never use `git add -A` or `git add .`
- Never commit sensitive files
- Always review staged changes before committing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |