Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill commit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Commit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-commit)More formats (shields.io, HTML) on the badges page.
---
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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!