Commit
Stage, commit, create PR, and merge to main. Use for the standard commit-PR-merge cycle.From its SKILL.md
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.7 KB, 409 tokens by cl100k_base, as published. Nobody here has run it
Commit, PR, and Merge
Stage changes, commit with a descriptive message, create a PR, and merge to main.
Steps
- Check current state:
git status
git diff --stat
git log --oneline -5
- Create a branch from the current state:
git checkout -b <short-descriptive-branch-name>
- Stage files — add specific files (never use
git add -A):
git add <file1> <file2> ...
Do NOT stage .claude/settings.local.json or any files containing secrets.
- Commit with a descriptive message:
If $ARGUMENTS is provided, use it as the commit message. Otherwise, analyze the staged changes and write a message that explains why, not just what.
git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
- Push and create PR:
git push -u origin <branch-name>
gh pr create --title "<short title>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>
## Test plan
<checklist>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
- Merge and clean up:
gh pr merge <pr-number> --merge --delete-branch
git checkout main
git pull
- Report the PR URL and what was merged.
Important
- Always create a NEW branch — never commit directly to main
- Exclude
settings.local.jsonand sensitive files from staging - Use
--merge(not--squashor--rebase) unless asked otherwise - If the commit message from
$ARGUMENTSis provided, use it exactly
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.