git-pushing
Safely stage, commit, and push intended git changes with conventional commit messages. Use for ordinary non-release pushes when explicitly asked to push, save work remotely, or share a completed change.
Profile →npx skills add sickn33/agentic-awesome-skills --skill git-pushing --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.
# Git Push Workflow Stage only intended changes, create a conventional commit, and push to the remote branch. ## When to Use Automatically activate when the user: - Explicitly asks to push changes ("push this", "commit and push") - Mentions saving work to remote ("save to github", "push to remote") - Completes a feature and wants to share it - Says phrases like "let's push this up" or "commit these changes" ## Safety Gates Before staging, inspect `git status --short --branch`, confirm the intended files, and fetch the upstream branch when a concurrent push is plausible. Do not absorb unrelated dirty files. Read repository policy before choosing the destination branch. If `main` or `master` is protected, or the repository defines a maintainer command such as `merge:batch`, create or use a topic branch and finish through the required pull-request checks. A user request to “push to main” describes the desired final state; it does not authorize bypassing server-side protection. Never keep retrying a direct push after a protected-branch rejection. The helper requires an empty live index and a conventional commit message before it stages anything. It locks the live index, builds and vali
- When to Use
- Safety Gates
- Workflow
- Limitations
bash "<skill-directory>/scripts/smart_commit.sh" bash "<skill-directory>/scripts/smart_commit.sh" "feat: add feature" bash "<skill-directory>/scripts/smart_commit.sh" "fix: scope change" -- path/to/file
What does the git-pushing skill do?
Safely stage, commit, and push intended git changes with conventional commit messages. Use for ordinary non-release pushes when explicitly asked to push, save work remotely, or share a completed change.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill git-pushing --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 sickn33/agentic-awesome-skills, a repository with 44,414 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.