Commit
🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库，覆盖8大社会科学学科的实证研究。CoPaper.AI 20分钟完成一篇可复现的规范实证论文，并支持用户上传 Skills。-- Maintained by CoPaper.AI from Stanford REAP.
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.
What its author says it does
Copied from the file, not written here
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".
SKILL.md
2.0 KB, as published. Nobody here has run it
Commit and Push
Stage changes, commit with a descriptive message, and push to remote.
Steps
- Check current state:
git status
git diff --stat
git log --oneline -5
- Create a branch from 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- Any files containing secrets or API keys
- Large data files (anything in
data/) - Temporary files (anything in
data/temp/)
- 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 <[email protected]>
EOF
)"
- 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
)"
- Merge and clean up (only if user confirms):
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 data files, temp files, and secrets from staging
- Use
--merge(not--squashor--rebase) unless asked otherwise - If the commit message from
$ARGUMENTSis provided, use it exactly - Follow existing commit message style (see recent
git log)