From swe
Use when user wants to commit changes, push code to remote, save work, or stage files for commit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/swe:git-commit-pushThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Commit changes and push to the remote repository using conventional commits format.
Commit changes and push to the remote repository using conventional commits format.
<type>: <description>
[optional body]
[optional footer]
Types:
feat - New featurefix - Bug fixdocs - Documentationrefactor - Code restructuringtest - Adding/updating testschore - Maintenance, dependenciesstyle - Code style changesperf - Performance improvementsgit status
Shows:
Before staging, review what changed:
git diff
git diff --staged # if anything is already staged
Stage all changes:
git add -A
Or stage specific files:
git add <file1> <file2>
Ask user or infer from context:
featfixdocsrefactortestchoregit commit -m "<type>: <short description>"
Examples:
git commit -m "feat: add user login form"
git commit -m "fix: resolve validation error on empty input"
git commit -m "docs: update API documentation"
git push -u origin <branch-name>
Report:
npx claudepluginhub peiyuanqi/work-like-me --plugin sweCommits all local git changes following Conventional Commits format with type, scope, and body, then pushes to remote. Analyzes diffs and logs for accurate messages.
Creates semantic git commits with conventional commit format, stages changes, and pushes to remote. Handles pre-commit hooks and writes meaningful commit messages.
Stages all changes, creates a conventional commit, and pushes to the remote branch in one step.