← LeaderboardThe Skill Leaderboard

commit

Stage, commit, and push changes for the sewage project. Creates a branch, commits with a descriptive message, pushes, and optionally creates a PR. This skill should be used when asked to "commit", "save changes", "push", or "create a PR".

Published by brycewang-stanford ↗brycewang-stanford/Auto-Empirical-Research-Skills

Try your first task

commit

Start a fresh conversation. Replace the highlighted placeholders.

Use commit to create a new branch, stage only [files to include], and commit them using [commit message]; exclude data, temporary files, secrets, and local settings, then stop and ask for my final confirmation before pushing or creating a pull request.

Required inputs

  • [files to include]
  • [commit message]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: commitdescription: Stage, commit, and push changes for the sewage project. Creates a branch, commits with a descriptive message, pushes, and optionally creates a PR. This skill should be used when asked to "commit", "save changes", "push", or "create a PR".argument-hint: "[optional: commit message]"allowed-tools: ["Bash", "Read", "Glob"]

Commit and Push

Stage changes, commit with a descriptive message, and push to remote.

Steps

  1. Check current state:
git status
git diff --stat
git log --oneline -5
  1. Create a branch from current state:
git checkout -b <short-descriptive-branch-name>
  1. Stage files — add specific files (never use git add -A):
git add <file1> <file2> ...

Do NOT stage:

  • .claude/settings.local.json
  • Any files containing secrets or API keys
  • Large data files (anything in data/)
  • Temporary files (anything in data/temp/)
  1. Commit with a descriptive message:

If $ARGUMENTS is provided, use it as the commit message. Otherwise, analyse the staged changes and write a message that explains why, not just what.

git commit -m "$(cat <<'EOF'
<commit message here>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
EOF
)"
  1. Push and optionally 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>
EOF
)"
  1. Merge and clean up (only if user confirms):
gh pr merge <pr-number> --merge --delete-branch
git checkout main
git pull
  1. Report the PR URL and what was merged.

Important

  • Always create a NEW branch — never commit directly to main
  • Exclude data files, temp files, and secrets from staging
  • Use --merge (not --squash or --rebase) unless asked otherwise
  • If the commit message from $ARGUMENTS is provided, use it exactly
  • Follow existing commit message style (see recent git log)