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".
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill commit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Commit and Push Stage changes, commit with a descriptive message, and push to remote. ## Steps 1. **Check current state:** ```bash git status git diff --stat git log --oneline -5 ``` 2. **Create a branch** from current state: ```bash git checkout -b <short-descriptive-branch-name> ``` 3. **Stage files** — add specific files (never use `git add -A`): ```bash git add <file1> <file2> ... ``` Do NOT
What does the commit skill do?
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".
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill commit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.