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.3 KB, 281 tokens by cl100k_base, as published. Nobody here has run it
Commit Workflow
Perform the full commit-PR-merge cycle.
Steps
-
Check current state:
git status git diff --stat git log --oneline -5 -
Create branch:
git checkout -b [descriptive-branch-name] -
Stage files:
- Stage specific files (never
git add -A) - Exclude:
settings.local.json,.env, credentials, large data files - Review what's being staged
- Stage specific files (never
-
Commit:
- Use
$ARGUMENTSas commit message if provided - Otherwise, analyze changes and write a descriptive message
- Format: imperative mood, concise, explains WHY not WHAT
- Use
-
Push and create PR:
git push -u origin [branch-name] gh pr create --title "[message]" --body "[summary of changes]" -
Merge (with user approval):
gh pr merge --merge --delete-branch git checkout main git pull
Important
- Never commit directly to main
- Never use
git add -Aorgit add . - Never commit sensitive files
- Always review staged changes before committing
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.